Skip to main content

Crypto Payment (Guest to Merchant)

CRYMBO Connect enables crypto payments from unregistered users (guests) to registered CRYMBO merchants. This is ideal for e-commerce, gaming, affiliates, or partner platforms that want to accept crypto without requiring user onboarding.

Use Case​

  • A merchant (CRYMBO user) generates a hosted payment link
  • A guest follows the link and completes payment in crypto
  • The funds are routed to the merchant’s CRYMBO wallet
  • The system monitors, verifies, and settles the transaction

Flow Overview​

  1. Merchant generates a payment link or widget
  2. Guest accesses hosted payment page
  3. Guest fills in required info (name, email, amount, coin)
  4. Guest sends crypto to the generated address
  5. CRYMBO tracks and verifies the payment
  6. Payment is settled to the merchant wallet upon confirmation

Step-by-Step​

1. Generate Payment Widget​

Admins or merchants can create a deposit widget via:

Endpoint:
POST /v3/deposits/create-widget

Payload:

{
	"merchant_id": "user_merchant123",
	"currency": "USDT",
	"amount": 150,
	"ref": "ORDER-4289342"
}

The guest opens the URL:

https://pay.crymbo.com/?deposit_token=XYZ

They see:

  • Coin selection (e.g. BTC, ETH, USDT)
  • Wallet address for deposit
  • Timer or expected confirmation window

3. Guest Makes the Payment​

  • Guest sends crypto to the displayed wallet address
  • The system begins watching the blockchain for the transaction
  • Optionally, the guest may receive a confirmation email

4. Transaction Monitoring & Matching​

Once the transaction is detected:

  • It's matched to the merchant’s reference
  • Travel Rule logic may be invoked depending on asset or thresholds
  • If KYT or metadata checks are triggered, they are enforced silently

5. Settlement to Merchant​

  • Funds are settled to the merchant’s internal CRYMBO wallet
  • Gas fees (if needed) are paid from the system Gas Wallet
  • The transaction appears in the merchant’s transfer history

Notes​

  • No registration or KYC is required from the payer (guest)
  • All merchant compliance is enforced via wallet metadata and KYT rules
  • Refunds or reversals must be handled via admin tools or merchant-side policy

Let me know if you’d like the next .md page for Wire Transfer Payments (Guest to Merchant).