Sandbox Portal
Manage API keys, simulate KYC approvals, and monitor operations
https://portal.sandbox.raliopay.com
https://portal.sandbox.raliopay.com
Sandbox API
Integration flow
Setup — API Keys & Webhooks
Every Ralio integration follows the same sequence. Each step depends on the previous one.
Verify the user (KYC / KYB)
Launch an identity verification session. In sandbox you approve it manually.
Create an account (Wallet)
Once the user is verified, create one or more accounts in any supported currency.
Fund the account (Payin)
Add funds via bank transfer, crypto deposit, or card. Simulate instantly in sandbox.
Move money — Transfer or Payout
Send funds internally between accounts (Transfer) or externally (Payout).
Setup — API Keys & Webhooks
Generate your API credentials and configure webhooks before making any API call.Step 1 — Generate API Keys
API Keys are managed exclusively from the Ralio Management Portal. You’ll need them to authenticate every API request.Open the Sandbox Portal
Step 2 — Authenticate (get a Bearer Token)
All API endpoints require a Bearer Token. Exchange your API Key for a token:200:
Step 3 — Configure Webhooks
Webhooks let your system react in real time to events without polling.Register your endpoint
Go to portal.sandbox.raliopay.com/account/webhooks
- Must be a valid
https://URL - Must accept
POSTrequests - Must respond with
2xxwithin 60 seconds
Available events
| Category | Events |
|---|---|
| Accounts | account.activated |
| Payins | payin.processing · payin.completed · payin.failed |
| Payouts | payout.processing · payout.completed |
| Transfers | transfer.processing · transfer.completed |
| KYC / KYB | kyc.state_updated · kyc.session_verified · kyc.session_failed · kyc.session_expired |
Create a user
Create individual (KYC) or business (KYB) users before issuing accounts or processing transactions.User types
Individual User
A natural person. Goes through KYC (Know Your Customer) verification.
POST /api/v1/account/individual-usersBusiness User
A legal entity / company. Goes through KYB (Know Your Business) verification.
POST /api/v1/account/business-usersVerify the user (KYC / KYB)
Launch identity verification sessions for users. In sandbox, approve or reject them instantly from the Portal.How it works
User completes verification
In production, the user follows the URL to submit documents.
In sandbox: skip this — approve directly from the Portal.
In sandbox: skip this — approve directly from the Portal.
Create an account (Wallet)
Create wallets for verified users. Required before any funding or payment operation.Create a user account
201:
Fund the account (Payin)
Add funds via bank transfer, crypto, or card. In sandbox, simulate funding instantly from the Portal.Payin methods
Bank Payin
User sends a bank transfer to an assigned IBAN. Ralio credits the account once the transfer settles.
Crypto Payin
User sends stablecoins to a generated wallet address. Auto-converted to account currency.
Card Payin
Payment via credit or debit card through an integrated payment gateway.
Simulate Bank Payin and Crypto Payin
Open the Sandbox Portal
Check payin details
Webhooks
| Event | When |
|---|---|
payin.processing | Payin detected, waiting for settlement |
payin.completed | Funds credited to the account |
payin.failed | Could not be processed |
Move money — Transfer or Payout
Move money internally between Ralio accounts (Transfer) or externally to a bank or crypto wallet (Payout).Transfer
Internal. Between two accounts inside Ralio. Instant, no external intermediaries.
Payout
External. To a bank account (IBAN) or crypto wallet address.
Transfers
Create a transfer
Webhooks
| Event | When |
|---|---|
transfer.processing | Being processed |
transfer.completed | Settled successfully |
Payouts
Bank PayoutCrypto PayoutWebhooks
| Event | When |
|---|---|
payout.processing | Submitted to network |
payout.completed | Funds delivered |
Orders
Every operation in Ralio (payin, payout, transfer) generates an Order. Orders are the central record of all operation attempts along with their statuses.Order States
| State | Meaning |
|---|---|
PENDING | Awaiting processing |
PROCESSING | Being processed |
COMPLETED | Settled → entry created in Ledger |
FAILED | Operation failed |
CANCELLED | Cancelled before completion |
Ledger
The Ledger is the system’s accounting ledger. It contains the immutable record of all transactions that have been successfully completed. Each Order in COMPLETED status generates an entry in the LedgerDifference between Orders and Ledger
| Orders | Ledger | |
|---|---|---|
| What it records | All operation attempts | Only completed operations |
| Statuses | PENDING, PROCESSING, COMPLETED, FAILED, CANCELLED | Only successful transactions |
| Main use | Real-time status tracking | Auditing and accounting |