0Bit Documentation

Cross-border platforms

Use 0Gate as a hosted funding, sell, or swap leg inside approved cross-border product flows.

Cross-border platforms can use 0Gate as the hosted payment, ramp, sell, or swap leg around their own product experience. 0Gate should not be documented as a blanket remittance, banking, payout, or corridor guarantee. Your product still owns its own user model, program rules, beneficiary experience, and jurisdiction-specific obligations.

Product split

AreaYour platform0Gate
User journeyChoose the cross-border use case, recipient workflow, internal ledger, and support model.Host the approved payment/ramp/swap session.
AvailabilityDecide what markets and flows your product can offer.Expose capability data and hosted flow outcomes where enabled.
Compliance wordingUse approved product, legal, and partner language.Provide hosted flow screens and event signals.
Final stateMark your transfer, balance, or account record from backend state.Send signed events and transaction references.

Safe implementation pattern

  1. Check whether the user, market, asset, currency, and flow are available for your product.
  2. Create a 0Gate session for only the hosted leg you are allowed to run.
  3. Keep recipient, transfer, or platform-specific business logic in your backend.
  4. Use 0Gate callbacks for UX and signed webhooks for durable state.
  5. Keep support records separate: your transfer id plus 0Gate session id, transaction ref, and event id.

Public copy guidance

AvoidPrefer
"Send money globally with 0Gate.""Use a hosted 0Gate flow where your account and market configuration support it."
"All corridors are available.""Check capability and product approval before displaying a route."
"Instant settlement guaranteed.""Use signed events and your own ledger state to show current status."
"0Gate replaces your compliance program.""0Gate hosts the approved ramp/payment experience; your product remains responsible for its own obligations."

On this page