FLUIDRWA RESEARCH
Ramp onboarding evidence map
MoonPay, Transak and Banxa across six buyer dimensions.
Reviewed by FluidRWA Research Team. Observations checked 7 Oct 2026. Research edition 2026-10-13.1.
Selection and method
Existing article cohort, not a ranked or exhaustive market sample. Official public documentation only; no authenticated APIs or production transactions tested.
Each record keeps the exact source, product scope, review date and unresolved question. Company documentation is company evidence, not independent validation. Not verified means insufficient reviewed evidence, not an absent feature.
No authenticated API calls, production onboarding, pricing, transaction speed or legal permissions were tested. No winner or vendor score is assigned. Rechecking a link alone does not change an observation's verification date.
| Provider / dimension | Observation | Scope | Unresolved question | Source / checked |
|---|---|---|---|---|
| MoonPayIntegration model | Widget API documentation covers buy/sell quotes and transaction lookups. | Widget API overview; not a review of every MoonPay product. | Not verified: eligibility for a specific partner, corridor or payment method. | Primary documentation7 Oct 2026 |
| MoonPayKYC hand-offs | Not verified: the complete KYC collection and reliance arrangement for the selected widget configuration. | Reviewed Widget API overview; insufficient evidence for a complete KYC responsibility map. | Request the collection, decision, retention and escalation responsibilities in writing. | Primary documentation7 Oct 2026 |
| MoonPayConfiguration discovery | The overview lists country, currency and payment-method discovery endpoints. | Endpoint discovery; not a live supported-country audit. | Not verified: the exact asset/network/method combination for the intended customer. | Primary documentation7 Oct 2026 |
| MoonPayOrder tracking | Widget webhooks document signed delivery, possible duplicates and out-of-order events. | Widget webhook lifecycle only. | Not verified: contracted support response and event retention. | Primary documentation7 Oct 2026 |
| MoonPayWallet / network controls | The buy-transaction response documents wallet address and currency network metadata. | Response fields, not a tested destination-address validation control. | Not verified: wallet ownership checks and wrong-network recovery. | Primary documentation7 Oct 2026 |
| MoonPayReconciliation | The buy response documents status, amounts, fees and a crypto transaction identifier. | API schema example; not an accounting export or completed transaction test. | Not verified: statement exports, settlement cut-offs and dispute adjustments. | Primary documentation7 Oct 2026 |
| TransakIntegration model | Whitelabel API limitations distinguish bank-transfer flows from semi-widget card/Apple Pay flows. | The API page lists OffRamp as unsupported in its limitations table. | Not verified: which features are enabled for a particular partner. | Primary documentation7 Oct 2026 |
| TransakKYC hand-offs | The API page distinguishes Lite KYC from a hosted Standard KYC document/liveness step. | Whitelabel journey; not a universal native onboarding claim. | Not verified: reliance acceptance, data retention and escalation for the buyer. | Primary documentation7 Oct 2026 |
| TransakConfiguration discovery | Public lookups and quotes support configuration discovery. | API documentation, not a live corridor coverage test. | Not verified: availability for the customer's exact geography and method. | Primary documentation7 Oct 2026 |
| TransakOrder tracking | Documentation provides order and KYC webhooks; production registration follows KYB approval. | Partner webhook integration. | Not verified: recovery guarantees, event retention and contracted support. | Primary documentation7 Oct 2026 |
| TransakWallet / network controls | Create Order documents a destination wallet and additional custodial-wallet information. | Whitelabel Create Order flow; not an ownership-check test. | Not verified: incorrect network/address handling and recovery. | Primary documentation7 Oct 2026 |
| TransakReconciliation | The API journey includes order-ID polling for final status. | Status polling, not evidence of a complete accounting feed. | Not verified: settlement exports and refund/fee-adjustment reconciliation. | Primary documentation7 Oct 2026 |
| BanxaIntegration model | Native integration uses API/SDK components; access requires an agreement. | Documentation labelled Beta (v0); Native is not self-serve access. | Not verified: partner access, version commitments and enabled payment methods. | Primary documentation7 Oct 2026 |
| BanxaKYC hand-offs | Identity/KYC documentation separates identity verification from transaction eligibility. | Native identity and eligibility flow. | Not verified: the buyer's approved KYC model and ongoing responsibilities. | Primary documentation7 Oct 2026 |
| BanxaConfiguration discovery | Configuration endpoints list methods, fiat, countries and cryptocurrencies. | Native configuration endpoints; not a production coverage test. | Not verified: exact customer, direction, amount and asset/network availability. | Primary documentation7 Oct 2026 |
| BanxaOrder tracking | Native webhooks describe ramp-status and identity-KYC notifications. | Signed webhook documentation, not a tested delivery guarantee. | Not verified: contracted replay, retention and escalation arrangements. | Primary documentation7 Oct 2026 |
| BanxaWallet / network controls | Configuration documentation supplies cryptocurrency choices for transaction setup. | Configuration scope only; destination-wallet controls were not established. | Not verified: wallet ownership, network enforcement and wrong-address recovery. | Primary documentation7 Oct 2026 |
| BanxaReconciliation | Ramp webhooks include amounts and fees; transaction hash is conditional on FULFILLED. | Webhook payload scope; not proof of bank settlement or ledger completeness. | Not verified: settlement statements, corrections and refund matching. | Primary documentation7 Oct 2026 |
Use this evidence in procurement
Ask each provider to confirm the exact product, customer jurisdiction, asset/network combination, KYC reliance, support arrangements and reconciliation evidence for your project. Do not treat a documented endpoint as a guarantee of eligibility.
Read the MoonPay, Transak and Banxa buyer comparisonVersion and corrections
2026-10-13.1: first Network Explorer publication of the existing 7 October documentation cohort. The original checked date is preserved. Scope corrections and future editions must be recorded separately.
Send corrections with primary evidence to contact@fluidrwa.com.
Build your infrastructure brief.
Identify the workflow and responsibilities you need to confirm.