Environments

• Production — https://api.paymnt.cloud
• Sandbox — https://sandbox.paymnt.cloud

​

Environment separation

• Data isolation. Objects created in Sandbox are not visible in Production, and vice versa.
• API keys. Generate separate secret keys per environment. Never reuse a Production key in Sandbox.
• Profiles & routing. Profiles (x-profile-id) are environment-scoped; configure routing independently per env.
• Connectors & credentials. Configure connector credentials separately for each environment.

Avoid real PII in Sandbox wherever possible. Use test data and anonymized payloads.

​

Authentication headers

api-key: <YOUR_SECRET_KEY>
x-profile-id: <pro_...>   # optional, when profiles are enabled

​

Pick the base URL

Base URL: https://sandbox.paymnt.cloud

Base URL: https://api.paymnt.cloud

# .env
PAYMNT_BASE_URL=https://sandbox.paymnt.cloud
PAYMNT_API_KEY=sk_sandbox_...

# on production deploy:
# PAYMNT_BASE_URL=https://api.paymnt.cloud
# PAYMNT_API_KEY=sk_live_...

const base = process.env.PAYMNT_BASE_URL;   // sandbox or prod
const res = await fetch(`${base}/customers`, {
  headers: { "Accept": "application/json", "api-key": process.env.PAYMNT_API_KEY }
});
const data = await res.json();
console.log(data);

​

Webhooks & events (managed — no self-hosted required)

1. In the Dashboard, enable event subscriptions for Sandbox or Production
2. Choose which event types you want to receive (e.g., payment lifecycle)
3. Consume events via our managed delivery or via the Events API (pull), depending on your integration preference

• Managed delivery (hosted by Paymnt Cloud). Events are delivered from our cloud; signature verification and retries are handled by the platform
• Events API (pull). Programmatically fetch and acknowledge events from the environment’s stream
• Optional external destination. If you still want to receive events at your own URL, you can add external endpoints; signing and retry/backoff apply the same way

​

Testing resources

• Sandbox guide — flows, test scenarios, configuration tips
• Test cards & 3DS — PANs, SCA outcomes, challenge flows

​

Rate limits and resilience

• Idempotency for POST/PUT/PATCH (Idempotency)
• Exponential backoff + jitter for transient failures (Retries & Backoff)
• Error handling with request_id logging (Error Codes)