One integration. Clear primitives. Complete visibility. A developer experience designed around the actual lifecycle of a payment.
Payments, refunds, routes and events are resources with stable identifiers. Amounts are integers in minor units; currencies are ISO 4217.
curl https://api.aegisrails.com/v1/payments \ -H "Authorization: Bearer sk_test_…" \ -H "Idempotency-Key: ord_10482" \ -d amount=12500 -d currency=USD
Send an Idempotency-Key on every write. A repeated request with the same key returns the original result instead of creating a second payment — essential when a network call times out.
req 1Idempotency-Key: ord_10482 → 201 createdOKreq 2Idempotency-Key: ord_10482 → 200 replayedOKresultone payment: pay_ag_8J29LEvents are delivered to your endpoint with a signature header and retried with backoff until acknowledged. Verify the signature before acting on the payload.
| EVENT | WHEN |
|---|---|
| payment.succeeded | authorised and captured |
| payment.failed | final decline returned |
| payment.requires_action | 3DS challenge needed |
| refund.succeeded | refund confirmed |
| route.degraded | route health changed |
Every error carries a stable type and code, a human message, and a request ID for support. Declines are not HTTP errors — they are payment outcomes.
{
"error": {
"type": "payment_error",
"code": "insufficient_funds",
"decline": { "issuer_code": "51" },
"request_id": "req_ag_91kd2"
}
}A sandbox environment with test keys and simulated issuer responses is planned. Test card numbers will trigger specific outcomes — approvals, declines, 3DS challenges, timeouts.
| TEST CARD | SIMULATES |
|---|---|
| 4000 …0002 | issuer decline 05 |
| 4000 …3220 | 3DS challenge |
| 4000 …0119 | processor timeout |
Let's discuss the infrastructure your business needs.