Revtain exposes a small set of free public endpoints that your team can call from anywhere — debugging tools, internal dashboards, fraud screens, support tools. They’re the same endpoints that power the live tools at revtain.com/tools. No authentication. No API key. CORS is open so you can call them from a browser as well as a server.Documentation Index
Fetch the complete documentation index at: https://docs.revtain.com/llms.txt
Use this file to discover all available pages before exploring further.
BIN Lookup
Identify the issuing bank, country, network, and card type from any 4 to 8 digit Bank Identification Number (BIN).| Field | Type | Description |
|---|---|---|
prefix | string | The BIN prefix you queried (4–8 digits). |
issuerName | string | The bank that issued the card, e.g. Chase, Barclays, Nubank. Unknown when not identifiable. |
issuerCountry | string | ISO-3166-1 alpha-2 country code, e.g. US, GB, BR. Unknown when not identifiable. |
cardNetwork | string | One of visa, mastercard, amex, discover, unknown. |
cardType | string | One of credit, debit, prepaid, unknown. |
400 Bad Request— prefix is not 4–8 digits.
Decline Code Lookup
Translate any gateway-specific decline code into Revtain’s canonical taxonomy with a plain-English explanation.{gateway} must be one of: stripe, braintree, adyen, checkout, authnet, dlocal, worldpay, razorpay, paystack.
Example:
| Field | Type | Description |
|---|---|---|
gateway | string | The gateway slug you queried. |
rawCode | string | The raw code you queried. |
canonicalCode | string | Revtain’s canonical taxonomy code (e.g. insufficient_funds, do_not_honor, expired_card). |
category | string | One of hard, soft, fraud, technical, auth_required, unknown. |
plainEnglish | string | A short, merchant-facing explanation of what this decline means. |
variantsOnOtherGateways | array | The same decline reason as it appears on other gateways. Useful for cross-gateway debugging. |
Full Decline Code Dictionary
Pull the entire decline-code dictionary in one call — 480+ codes across 9 gateways, grouped by canonical category.Use cases
- Internal debug dashboards — show your support team a plain-English meaning for every decline the gateway returned.
- Customer support scripts — let agents type in a raw code from a transaction log and immediately see what to tell the customer.
- Fraud / risk screens — enrich a transaction view with
issuerNameandissuerCountrywithout integrating a paid BIN service. - Engineering — wire the canonical decline taxonomy into your own retry logic if you don’t use Revtain for everything.
Rate limits
There are no per-key rate limits on these endpoints (they take no auth). We ask that you cache responses where reasonable — the underlying data updates infrequently:- BIN responses can be safely cached for 24 hours per prefix.
- Decline-code responses can be safely cached indefinitely; the dictionary changes only when we add new gateway support.