API Reseller
Credit Card Bill Payment API
Credit card bill payment by card number and issuer, settling to the cardholder account. Validation runs before submission so an incorrect card number is refused rather than sent into the network.
What you get
- Payment to cards issued by any major bank
- Card number validation before submission
- Amount and due-date fetch where the issuer supports it
- Confirmation reference for the cardholder statement
- Explicit pending state until the issuer confirms
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Input
- Card number and amount. No card is stored at any point.
- Idempotency
- Keyed on your own reference, so a retry cannot pay a bill twice.
- Timeout
- Stays pending with the wallet debited. Never auto-failed on elapsed time.
- Webhook
- Signed, with replay protection. Retried until your endpoint returns 2xx.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About credit card bill payment api
Is the card number stored anywhere?
No. It is used for the payment and not retained, which keeps the card data out of your systems and ours. Nothing about a completed payment requires storing the number.
A payment timed out. Can I safely submit it again?
Only with the same reference. Reusing it returns the original payment rather than creating a second one. A timeout is the case where the payment is most likely to have succeeded, so submitting with a fresh reference is how a customer's card bill gets paid twice.