Crypto Transfer
Crypto Transfer lets Payers pay by sending crypto directly on-chain to a Yugo-managed deposit address on a supported blockchain network.
API value: payment.method = crypto_transfer
Authorization Flow
- The Payer is redirected to Yugo Checkout
- Yugo displays the deposit address and blockchain network for the Payin
- The Payer sends crypto from their own wallet to that address
- Once the on-chain transfer is broadcast, the Payer is returned to the Merchant
- Yugo waits for the required number of confirmations before marking the Payin as
RECEIVED
Off-Session Transfers
Once a deposit address has been issued to a Payer for a given crypto asset and network, the Payer can reuse it to send funds at any time — without re-entering Yugo Checkout or going through the Merchant's UI again.
When such an off-session transfer is detected on-chain, Yugo:
- Registers a Payin transaction against the Merchant and the originating Payer
- Runs it through the same status lifecycle (
RECEIVED→SETTLED→COMPLETED) - Sends a webhook to the static webhook URL configured during the Merchant's onboarding
info
The webhook destination for off-session transfers is fixed at onboarding and is not configurable per Payin. Make sure the endpoint is stable and able to handle Payin notifications that were not initiated by an explicit Payin Intent.
Processing Timeline
| Stage | Timing |
|---|---|
| On-chain broadcast | Real-time (initiated by the Payer) |
| Confirmation | Depends on the blockchain network |
| Settlement to Merchant wallet | Immediately after confirmation |
Method-Specific Behavior
- No chargeback or dispute risk — on-chain transfers are irrevocable once confirmed
- The
DISPUTEDstatus does not apply to Crypto Transfer Payins - Supported crypto assets and blockchain networks are configured during onboarding
- Off-session deposits to a known address generate Payin transactions automatically