Skip to main content
Use the test credentials on this page to simulate successful, declined, and failed payments in test mode. No money moves, and no real account is charged. To see a complete test payment, watch this video.

Full API Access

Every API endpoint is available in test mode.

Webhook Testing

Webhooks fire for test transactions the same way as in production.
Test credentials work only in test mode. In live mode, a payment made with a test credential fails.

​
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.

​
Testing Renewal Failures

1

Create a test subscription

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

Update the payment method

Open the Customer Portal, find the subscription, and click Update Payment Method. Enter the failure test card 4000000000000341 (Expiry: 12/34, CVV: 123) and save it.
3

Advance the next billing date (optional)

To trigger renewal without waiting for the natural billing cycle, use the Update Subscription API to set next_billing_date to a time slightly in the future, such as one minute from now. Replace the example value below. The API rejects a next_billing_date that is not in the future, including the current 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 Past Due first (the grace period; the subscription.past_due webhook carries past_due_ends_at), then to On-Hold when the grace period ends
  • A payment.failed webhook event is delivered
  • The customer can return to the Customer Portal to update the payment method and retry

​
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 Pix

Pix testing uses a test CPF (Brazilian tax ID) to simulate the QR code flow.

​
Requirements for Pix Testing

  • Billing country must be set to BR
  • Currency must be BRL
Enter the test CPF when prompted at checkout. A test QR code is generated — scan it with your phone’s normal camera (no Pix app needed) and you’ll be redirected to a test page where you can simulate the transaction as a success or failure. For complete Pix documentation, see the Pix 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:
On USD checkouts, 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.
On USD checkouts, 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

Turn off the Live Mode switch in the dashboard sidebar, and use API keys created in test mode. See Test Mode vs Live Mode.
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

Turn off the Live Mode switch in the dashboard sidebar, and use API keys created in test mode. See Test Mode vs Live Mode.
3

Complete test purchase

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

​
Amazon Pay, Cash App Pay, and 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

Turn off the Live Mode switch in the dashboard sidebar, and use API keys created in test mode. See Test Mode vs Live Mode.
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.
Multibanco shows a voucher instead of a bank flow. See Test Multibanco.
1

Enable test mode

Turn off the Live Mode switch in the dashboard sidebar, and use API keys created in test mode. See Test Mode vs Live Mode.
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 Multibanco

Use EUR and a PT billing address. After you click Pay, checkout shows a Multibanco voucher. In test mode, the email you enter decides the result: To see the success page, use succeed_immediately@example.com, wait a few seconds, and tap Done. For the full list of test emails, see the Europe page.

​
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.

​
Test Asia-Pacific Wallets

GCash, Alipay HK, FPS, and Touch ‘n Go are QR code payments that only appear when the billing country and currency match.
1

Enable test mode

Turn off the Live Mode switch in the dashboard sidebar, and use API keys created in test mode. See Test Mode vs Live Mode.
2

Set billing country and currency

Create a one-time checkout with the matching pair:
3

Select the method and confirm

Select the method and click Pay. A QR code opens in a full-screen overlay and the checkout waits for the payment.
4

Verify the checkout behavior

Confirm the method appears only for the matching country and currency and the QR code renders.
Test-mode QR codes are issued by the wallet provider’s test environment and may behave differently from a live payment.
For complete documentation, see the Asia-Pacific page.

​
Testing Best Practices

Don’t test only 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.
Klarna and Afterpay require a $50.01 minimum on USD checkouts. Test that they correctly appear or 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.

Pix

Pix testing with test CPF.

Europe

iDEAL, Bancontact, EPS, Multibanco testing.

Asia-Pacific

GCash, Alipay HK, FPS, and Touch ‘n Go testing.

Webhooks

Set up webhooks for test events.

CLI Webhook Testing

Test webhooks locally with the Dodo Payments CLI.
Last modified on October 6, 2026