Channel Payments
The Channel Payments page lists every inbound payment that has hit any of your channels. Use it to confirm a customer's deposit, reconcile against an on-chain transaction, or check the outcome of compliance screening on a specific payment.
The payment list
Each row is one inbound channel payment. The columns are:
| Column | What it shows |
|---|---|
| Uuid | The payment's unique identifier. Use this when filing support tickets or calling the API. |
| Reference | The reference of the channel that received the payment — inherited from the channel's Reference field. |
| Status | The current state of the payment. COMPLETE means BEEM has finalised the payment and credited the wallet. |
| Paid Currency | The asset the customer sent (the channel's Pay Currency). |
| Paid Amount | The amount received on-chain, denominated in the Paid Currency. |
| Wallet Currency | The currency of the wallet that received the converted funds. |
| Wallet Amount | The amount credited to the wallet, after conversion from Paid Currency to Wallet Currency. |
| Was On Hold | Whether the payment was held for compliance screening at any point. False means it cleared with no manual review; True means it was held and subsequently released. |
Searching
Use the Search by hash field at the top of the list to find a payment by its on-chain transaction hash. This is the fastest way to confirm a specific deposit when a customer (or your finance team) provides the on-chain reference.
The hash matches the transaction on the network the customer paid on — whichever network they chose from the channel's set of addresses.
Conversion and the two amount columns
A channel payment has two amounts because the customer pays in one currency and the wallet settles in another:
- Paid Amount in Paid Currency is what arrived on-chain. This is the figure you can verify on a block explorer.
- Wallet Amount in Wallet Currency is what was credited to the wallet after BEEM's conversion. This is the figure your finance team sees on the wallet balance.
The conversion rate applied to each payment is recorded against the payment so both legs reconcile cleanly.
Compliance and "Was On Hold"
Every inbound payment passes through BEEM's compliance screening before it is finalised. If a payment triggers a screening rule, it is held for review and does not credit the wallet until it clears.
| Was On Hold | What happened |
|---|---|
False | The payment cleared screening automatically. No manual intervention. |
True | The payment was held for review and was subsequently released and credited. |
Held payments remain visible on this page throughout their lifecycle so your operations team can see and follow up.
For the conceptual background on what triggers a hold, see the Compliance and holds section on the Channels Overview.