Traceability & credit consumptions

Track how credits flow between inbound and outbound wallet transactions.

Wallet traceability lets you follow the credit flow between inbound (top-up) and outbound (usage deduction) transactions. For a given inbound transaction, you can see which outbound transactions consumed its credits — and for a given outbound transaction, you can see which inbound transactions funded it.

Track how credits were consumed

For an inbound wallet transaction, you can see all outbound transactions that consumed credits from it.

Dashboard

1. Go to a specific customer;
2. Open the “Wallets” tab and click on a specific wallet;
3. Click on an inbound wallet transaction;
4. Go to the “Consumptions” tab; and
5. See all outbound wallet transactions linked to this top-up and the amount consumed by each.

API

List consumptions for a wallet transaction

LAGO_URL="https://api.getlago.com"
API_KEY="__YOUR_API_KEY__"

curl --location --request GET "$LAGO_URL/api/v1/wallet_transactions/:lago_id/consumptions" \
  --header "Authorization: Bearer $API_KEY"

Track how credits were funded

For an outbound wallet transaction, you can see all inbound transactions that funded it.

Dashboard

1. Go to a specific customer;
2. Open the “Wallets” tab and click on a specific wallet;
3. Click on an outbound wallet transaction;
4. Go to the “Fundings” tab; and
5. See all inbound wallet transactions that funded this deduction and the amount each provided.

API

List fundings for a wallet transaction

LAGO_URL="https://api.getlago.com"
API_KEY="__YOUR_API_KEY__"

curl --location --request GET "$LAGO_URL/api/v1/wallet_transactions/:lago_id/fundings" \
  --header "Authorization: Bearer $API_KEY"

Route events to a specific wallet

Overview

Events can target a specific wallet. When calculating usage or applying credits for such events, credits are drawn from the targeted wallet rather than following the standard wallet selection logic.

If a target_wallet_code refers to a wallet that does not exist, no credits will be applied for that event.

Requirements

To use wallet-targeted events, two things must be configured:

1. Update the charge to set: accepts_target_wallets: true
2. Include target_wallet_code in the event payload

{
  "event": {
    "transaction_id": "...",
    "external_subscription_id": "...",
    "code": "...",
    "target_wallet_code": "my_wallet_code",
    "properties": { }
  }
}

Behavior

Charge accepts_target_wallets	Event target_wallet_code	Result
true	Valid wallet code	Credits are drawn from the targeted wallet
true	Invalid / non-existent wallet code	No credits are applied
true	Not provided	Standard wallet selection logic is applied
false	Any value	Standard wallet selection logic is applied (target is ignored)

• A charge with accepts_target_wallets: true does not require every event to carry a target_wallet_code. Events without a target fall back to the standard logic.
• Ensure the target_wallet_code matches an existing wallet’s code on the customer, otherwise the event produces no credit application.