RMO Developers
← rmous.org Merchant Services →

Test Credentials

A shared Public Sandbox tenant is pre-configured at api.rmous.org. Copy the keys below and start building — no signup, no email, no waiting.

How modes work. The base URL is the same for test and live: https://api.rmous.org. The API key prefix selects the mode — pk_test_… is sandbox, pk_live_… is production. Test-mode authorizations never settle to a real account.

Shared sandbox keys

Use these exact strings as-is. They’re intentionally not secret — every developer shares them while exploring.

API Key (public identifier)
pk_test_publicsandbox_2026
Bearer Secret
sk_test_publicsandbox_2026_anyone_can_use_this
Base URL
https://api.rmous.org

Try it in 30 seconds

Paste this into your terminal. You should see the tenant identity come back.

curl https://api.rmous.org/v1/me \
  -H "X-API-Key: pk_test_publicsandbox_2026" \
  -H "Authorization: Bearer sk_test_publicsandbox_2026_anyone_can_use_this"

# Expected response:
# {
#   "id": "pSYuEBn5k3PDjrW4z",
#   "title": "Public Sandbox",
#   "slug": "public-sandbox",
#   "environment": "test",
#   "rateLimitTier": "basic",
#   "requireSignature": false,
#   "status": "Processor Active"
# }

Sandbox characteristics

SettingValue
Environmenttest
Rate limit10 req/sec, 100,000 requests/day (shared across all sandbox users)
Signing requiredNo (HMAC X-Signature optional)
IP allowlistNone (any source)
SettlementNone — test-mode authorizations are audit-only
Webhook deliverySame delivery worker, same signatures, real HTTPS POSTs to your endpoint
Shared tenant warning. Because the sandbox is shared, every developer can see every other developer’s test authorizations and webhook subscriptions on this tenant. Never put real customer data through the public sandbox.

Moving to production

Live access (real settlement, dedicated tenant, your own keys) is provisioned through RMO Merchant Services. To request:

  1. Visit RMO Merchant Services to review processing tiers, settlement timing, and pricing.
  2. Submit the M.A.P.S contact form with your company name, integration type (merchant / processor / platform), and expected monthly transaction volume.
  3. You’ll receive an onboarding packet covering the network agreement, settlement timing, fees, and compliance attestations.
  4. Once signed, we mint your pk_live_* + sk_live_* pair, set your rate-limit tier, and (optionally) configure HMAC signing + IP allowlist.
Merchant Services → Contact RMO →

Next steps

Quickstart → Auth model → Authorize a card →