Skip to main content

Regulated Crypto Payment (Guest Onboarding)

This payment flow supports crypto payments from external users who are not associated with any merchant, but must be onboarded into CRYMBO for compliance.

While the funds are routed to the merchant, the guest becomes a registered CRYMBO user, enabling compliance checks such as KYC, TLV (Total Lifetime Value) limits, and risk scoring.

Use Case​

  • A merchant sends a payment link to a new guest
  • The guest pays in crypto but exceeds a compliance threshold
  • CRYMBO requires the guest to register, complete PII/KYC
  • The guest is onboarded as a system-level user (not owned by the merchant)
  • The payment is routed to the merchant wallet upon confirmation

Flow Overview​

  1. Guest opens a merchant-hosted deposit link
  2. Guest completes initial payment form
  3. If TLV exceeds threshold → Onboarding is required
  4. Guest registers and submits PII and/or KYC
  5. CRYMBO verifies compliance
  6. Funds are routed to the merchant wallet

Step-by-Step​

Guest accesses a CRYMBO payment link:

https://pay.crymbo.com/?deposit_token=XYZ
  • Refers to a deposit associated with a merchant wallet
  • Includes requested amount and currency

2. Threshold Evaluation (TLV)​

Before allowing a blockchain payment:

  • CRYMBO evaluates the user’s existing TLV
  • If TLV + deposit amount > limit, onboarding is triggered

The TLV thresholds are defined by system rules (e.g. €1000 for anonymous users).

3. Guest Registration & PII​

If the guest is unregistered or over the threshold:

  • They are redirected to a registration form
  • Must complete:
    • Email verification
    • PII form (name, address, etc.)
    • Questionnaire
    • KYC (if threshold exceeded or flagged)

They are now treated as a CRYMBO user, not attached to the merchant.

4. Crypto Payment​

Once cleared:

  • Guest is given a crypto address to pay
  • Sends crypto to the wallet linked to the deposit token

5. Transaction Monitoring​

  • CRYMBO blockchain listeners track the transaction
  • Once confirmed:
    • The deposit is assigned to the merchant
    • The user record is updated with TLV and compliance flags

6. Admin Oversight​

Admins can:

  • See the deposit record (payer = user, recipient = merchant)
  • Audit the user onboarding steps
  • Approve or reject the transaction based on risk rules

Summary​

  • Guests become system users if TLV triggers onboarding
  • Funds always go to the merchant, not the guest
  • CRYMBO enforces compliance centrally, even in merchant-driven flows