Test recurring payments

Test your integration in sandbox before you charge real customers. Use your sandbox credentials with the base URL https://sandbox.nomba.com. For setup, see Sandbox testing. Sandbox checkout endpoints start with /sandbox/checkout/ instead of /v1/checkout/:

​

1. Test the card-saving payment

Create a sandbox checkout order with "tokenizeCard": true, open the checkoutLink, and pay with this card: Any expiry date, CVV and PIN work in sandbox. Only the card number decides the outcome. Check that your webhook handler receives payment_success. Because sandbox doesn’t return a token, use any test value, such as test-token-1, as the tokenKey in the next steps.

​

2. Test a charge

Send a charge to /sandbox/checkout/tokenized-card-payment with any tokenKey: Sandbox can’t return otpRequired: true for a saved-card charge, so you can’t trigger the OTP challenge from a charge.

​

3. Test OTP submission

To test your OTP screen and request, call /sandbox/checkout/checkout-card-otp with any orderReference and transactionId. The otp decides the outcome:

​

4. Test managing saved cards

​

Checklist before you go live

• A card-saving payment stores the tokenKey against the right customer, and falls back to listing saved cards if the webhook has no token.
• An approved charge gives value once, and only after you’ve verified it.
• An OTP charge notifies the customer, accepts the code, and completes.
• A timed-out or wrong OTP leaves the subscription unpaid and is retried with a new orderReference.
• A declined charge is retried later, not straight away.
• A request that timed out is retried with the same orderReference, then verified.
• A duplicate webhook doesn’t give value twice.
• Your webhook handler rejects payloads with an invalid signature.
• A deleted card is removed from your database and isn’t charged again.
• You’ve switched to production credentials and https://api.nomba.com, and run one real charge with a small amount.