Crypto Transfer → Crypto (Yugo wallet)

Receive crypto payments and settle as crypto in a custodial Web3 wallet managed by Yugo.

Payment method: crypto_transfer | Settlement method: yugo_balance

Prerequisites

Before using this flow, you must be onboarded as a Merchant with Yugo and have a merchant account opened.

During onboarding, Yugo configures:

• Supported crypto assets
• Supported blockchain networks
• A custodial Web3 wallet managed by Yugo
• A webhook URL where Yugo notifies you of received funds
• An account with access to the Yugo Business Portal, where you retrieve your API Key and Webhook secret

Some of these settings are configured during onboarding and are not passed dynamically in each API request — check the API Reference for the exact request fields.

1. Create the Payin Intent

API Reference: POST /payins View Create Payin API →

Minimal Payin Intent Request

{
  "amount": {
    "value": "100.00",
    "currency": "EUR"
  },
  "payer": {
    "email": "payer@example.com",
    "first_name": "John",
    "last_name": "Doe",
    "country": "DE"
  },
  "reference": "order_123",
  "return_url": "https://merchant.com/checkout/complete",
  "webhook_url": "https://merchant.com/api/webhooks/payins",
  "payment": {
    "method": "crypto_transfer"
  },
  "settlement": {
    "method": "yugo_balance"
  }
}

Key fields:

• payment.method = crypto_transfer — triggers the Crypto Transfer flow
• settlement.method = yugo_balance — funds are delivered to the Merchant's custodial wallet

2. Redirect the Payer

The Payin response contains a redirect_url. Redirect the Payer to this URL to continue the payment.

At this point:

• Yugo hosts the checkout experience (in some cases this step is skipped)
• The Payer completes the authorization flow for their chosen payment method
• After completion, the Payer is redirected back to the Merchant's return_url

tip

The more payment details the Merchant supplies when creating the Payin Intent, the less friction for the Payer after redirect. In some cases, the Payer may be redirected directly back to the Merchant.

Yugo presents the Payer with the blockchain address (and network) where funds must be sent. The Payer signs and broadcasts the on-chain transfer from their wallet, then is redirected back to the Merchant's return_url. See Crypto Transfer.

3. Track Payin Status

Option A: Webhooks

Yugo sends a webhook every time the Payin status changes.

When you receive a webhook, we recommend verifying the updated status via the API (Option B).

API Reference: View Webhook Reference →

Option B: Polling

You can retrieve the current Payin status at any time.

API Reference: GET /payins/{id} View Get Payin API →

Status Lifecycle

See the Payin Status Lifecycle for the full state diagram and status definitions per payment and settlement method combination.

Status	Meaning
CREATED	Payin Intent created by Merchant
INITIATED	Deposit address generated and shared with the Payer
AUTHORIZED	Payer broadcast the crypto transfer on-chain
RECEIVED	Yugo confirmed receipt of the crypto funds on-chain
SETTLED	Crypto delivered to the Merchant's custodial wallet
COMPLETED	Transaction finalized.
FAILED	Transfer failed or was rejected
EXPIRED	Payin session expired before funds were received

Safe to release goods or services to the Payer from this status.

Deep dive

• Crypto Transfer — on-chain deposit flow, confirmation timing
• Yugo Balance Settlement — settlement and fund management
• Status Lifecycle — full state diagram and status definitions
• Create Payin API — request/response schemas and all fields