Trust & fund flows
Who holds your money,in plain language.
This page is versioned with our compliance posture and says only what we can back today. Where a licensed partner controls an outcome, we say “the partner controls this” — we don’t dress their policy up as our promise.
The structural fact
APXRAILS never holdsbuyer funds.
In our current posture, APXRAILS operates as a technology and orchestration layer. Licensed partners are always the regulated principal: they accept the buyer’s payment, hold the funds, and settle to you. Buyer money never passes through an APXRAILS account — not even transiently — and we never take unilateral control of anyone’s crypto keys. Every balance in the dashboard is labeled with its custodian, because “your balance” should always answer the question “held by whom?”.
Card payments
Who holds the funds
The licensed payment provider (named in your merchant agreement) — you are their merchant of record; funds settle from them to you
Where you see it
Balance labeled “Held at [provider]” until payout
Card-to-crypto acceptance
Who holds the funds
The licensed acquirer as principal: accepts fiat from the buyer, settles crypto directly to your wallet
Where you see it
Settlement to your own wallet address, verified at onboarding
On/off-ramp flows
Who holds the funds
The licensed ramp provider as merchant of record; crypto is delivered to the end user’s own verified wallet — never routed through you or us
Where you see it
Provider identity and authorization disclosed inside the flow, before KYC
Refunds & disputes
Who holds the funds
Reverse flows run on the same partner rails as the original payment — the partner debits your balance or reserve, never an APXRAILS account
Where you see it
Refund and dispute objects with full fee and ledger detail
Reserves & holds
Every hold: the reason, thetimeline, who imposed it.
Transparency about reserves — not their absence — is the differentiator. High-risk acceptance genuinely requires them; hiding them until your first payout is the industry’s worst habit.
Terms
Published per risk tier
Attribution
Ours vs. theirs, labeled
SLA
Published escalation SLA
Security
Card data we structurallycannot see.
Security posture as architecture, not as a badge wall.
PCI scope
Provider-hosted card fields — always
Ledger
An append-only ledger
Integrity
Signed webhooks, idempotent APIs
Onboarding
KYB before live mode
Scope
What this page is not.
APXRAILS is not a bank, payment institution, e-money institution or licensed crypto-asset service provider, and this page is not a claim to be one. Regulated services are provided by licensed partners, named in your merchant agreement and disclosed in-flow wherever a regulated step occurs. As our compliance posture evolves, this page changes with it — versioned, in the open. For what we simply don’t offer yet, read what we don’t do yet.