RAMBOCARD GUIDE · 2026-07-29
RamboCard API Onboarding Documents: Merchant Identity, Website and Risk Review
What RamboCard API merchants should prepare before production card issuing access.
API overview
Commercial API access needs merchant identity evidence and risk review, even when sandbox is available early.
RamboCard explains wallet funding, card issuing, card top-ups, service fees, notifications and reconciliation in one product workflow.
Minimum documents
A practical onboarding flow can request merchant identity evidence, business or personal proof where applicable, issuing website URL and contact information. The goal is to verify who operates the integration and what card use case they will support.
Automatic vs manual review
Automatic review can use a fixed deposit requirement and standard terms. Manual review can be used for negotiated business terms, special deposit requirements or custom fee policy.
After submission
Submitting documents should return the user to the application page with a clear progress state. Only fully approved merchants should enter production workspace automatically.
Sandbox first
Merchants can receive sandbox access before production deposit if policy allows. Sandbox lets them test integration without creating real cards or calling upstream production issuing.
Launch checklist
- Confirm the relevant RamboCard account, wallet, card, API merchant or transaction record before taking action.
- Keep RamboToken USDT wallet records, platform USD records, card balances and API merchant reserve records separate.
- Show fees, minimums, card program status and restrictions before the user confirms a financial operation.
- Send email notifications for material wallet movement, card charges, failed payments, low balance, refunds, chargebacks and card status changes where the platform receives the event.
- Use backend policy as the source of truth. Frontend pages should explain, display and refresh state, not create financial authority by themselves.
FAQ
Does sandbox require full production approval?
Not necessarily. RamboCard can allow sandbox for technical testing while production remains blocked.
What is the key required document?
Merchant identity proof and a clear website or use-case explanation are core risk review materials.
Who can set special terms?
Only RamboCard admin in the system backend should set special deposit or fee terms.