Skip to main content

​
Overview

Test mode lets you simulate payments without processing real transactions. All test credentials only work in test mode — never use them in production.

No Real Charges

Test transactions don’t process actual payments or affect real accounts.

Full API Access

All API endpoints work identically in test and live modes.

Webhook Testing

Webhooks fire for test transactions just like production.
Test credentials only work in test mode. Attempting to use them in live mode will result in payment failures.

​
Test Cards

Use these card numbers to simulate successful and declined payments across different regions.
For all test cards, use expiry date 06/32 (or 12/34) and CVV 123.

​
How to Test Renewal Failure

1

Create a test subscription

Create a subscription with your test API keys using a success test card (for example, 4242 4242 4242 4242). The initial charge should succeed and the subscription should become active.
2

Swap in the failure card via Customer Portal

Open the Customer Portal, find the subscription you just created, and click Update Payment Method. Enter the failure test card 4000 0000 0000 0341 (Expiry: 12/34, CVC: 123) and save it as the subscription’s payment method.
3

Advance the next billing date (optional)

To trigger renewal immediately instead of waiting for the natural billing cycle, use the Update Subscription API to set next_billing_date to the current UTC time. The value must be an ISO 8601 / RFC 3339 UTC timestamp (the Z suffix is required).
See the Update Subscription API reference for details.
4

Verify the failure

On the next billing attempt:
  • The renewal charge declines on the failure card
  • The subscription moves to On-Hold status
  • A payment.failed webhook event is delivered
  • The customer can return to the Customer Portal to update the payment method and retry
This card is specifically for testing renewal failures. The charge will decline on the next billing date, allowing you to test payment retry logic, customer notifications, and failure handling.

​
Test UPI

UPI testing uses special VPA (Virtual Payment Address) identifiers that simulate different payment outcomes.

​
Requirements for UPI Testing

  • Billing country must be set to IN
  • Currency must be INR
  • For non-Indian merchants: Adaptive Currency must be enabled
For complete UPI documentation including RBI mandate testing for subscriptions, see the India Payment Methods page.

​
Test BNPL

Buy Now Pay Later providers have specific test data requirements.

​
Klarna Test Data

Use these details to simulate Klarna payments in test mode:
Klarna requires a minimum transaction amount of $50.01 to appear as a payment option.

​
Afterpay Testing

1

Select Afterpay

Choose Afterpay as the payment method in checkout and click Pay.
2

Test successful payment

Use any valid email address and shipping address for successful payments.
3

Test failed authentication

To simulate failure, close the Afterpay modal window on the redirect page. The payment transitions from requires_customer_action to requires_payment_method.
Afterpay requires a minimum transaction amount of $50.01 to appear as a payment option.
For complete BNPL documentation including Billie B2B testing, see the Buy Now Pay Later page.

​
Test Digital Wallets

​
Apple Pay

1

Enable test mode

Use your Dodo Payments test API keys.
2

Add a card to Apple Wallet

Add a real card to your Apple Wallet. In test mode, the card won’t be charged.
3

Complete test purchase

Open checkout on an Apple device and complete the Apple Pay flow.
Apple Pay requires HTTPS. It won’t appear on localhost without proper SSL setup. Domain verification must also be complete.

​
Google Pay

1

Join the test card group

Join the Google Pay test card group to get test cards automatically added to your wallet.
2

Enable test mode

Use your Dodo Payments test API keys.
3

Complete test purchase

Select one of the test cards in Google Pay to complete the transaction.

​
Amazon Pay, Cash App Pay & RevolutPay

Use your test API keys and follow the standard checkout flow. Test transactions are simulated without actual charges. For complete digital wallet documentation including domain verification for Apple Pay, see the Digital Wallets page.

​
Test ACH Direct Debit

ACH Direct Debit can be tested in Test Mode by entering test bank details at checkout.
1

Enable test mode

Use your Dodo Payments test API keys.
2

Set currency and billing address

Set the billing currency to USD and the billing address country to US. ACH is not offered outside this combination.
3

Use a one-time payment

ACH is not available on subscription checkouts, so test it against a one-time payment.
4

Enter the test bank details

Enter one of the test routing and account number pairs below, then confirm your webhook handler receives the final payment status — ACH payments confirm asynchronously rather than at checkout.

​
Test Bank Accounts

Use the routing number 110000000 with any of these account numbers: For the full list of test accounts, see the ACH Direct Debit page.

​
Test European Methods

European payment methods (iDEAL, Bancontact, EPS, Multibanco) can be tested in Test Mode.
1

Enable test mode

Use your Dodo Payments test API keys.
2

Set billing address

Set the billing address country to match the payment method:
  • NL for iDEAL
  • BE for Bancontact
  • AT for EPS
  • PT for Multibanco
3

Set currency

European methods require EUR currency.
4

Complete test flow

Follow the simulated bank authentication flow in the test environment.

​
Test SEPA Direct Debit IBANs

SEPA Direct Debit requires EUR and a Eurozone billing address. Use these test IBANs to force a specific outcome: For the full list of test IBANs, including per-country values, see the Europe page. For complete European payment methods documentation, see the Europe page.

​
Testing Best Practices

Don’t just test successful payments. Test declines, cancellations, and edge cases like insufficient funds.
Ensure your webhook endpoints correctly process all event types, especially payment.succeeded, payment.failed, and subscription events.Use the Dodo Payments CLI to test webhooks locally:
  • dodo wh listen forwards live test webhooks to your local server
  • dodo wh trigger sends mock payloads for all supported webhook event types
For Apple Pay and Google Pay, test on actual iOS and Android devices. Simulators don’t fully replicate wallet behavior.
Regional payment methods (UPI, iDEAL, etc.) require matching billing addresses. A US billing address won’t show iDEAL.
BNPL methods require $50.01 minimum. Test that they correctly appear/hide based on cart total.

Cards

Card testing, 3D Secure, and saved payment methods.

Digital Wallets

Apple Pay, Google Pay, Amazon Pay testing.

BNPL

Klarna, Afterpay, and Billie testing.

India

UPI and RBI mandate testing.

Europe

iDEAL, Bancontact, EPS, Multibanco testing.

Webhooks

Set up webhooks for test events.

CLI Webhook Testing

Test webhooks locally with the Dodo Payments CLI.
Last modified on August 13, 2026