Integration Testing

Overview

To ensure your integration with Moment APIs functions correctly, you can simulate payment flows during development. This allows you to test various scenarios without any real money movement.

Testing Cards

When testing card payments, always use test API keys. Only use the specified test cards listed below. Do not use real card information under any circumstances.

Note: The 3DS challenge page will not be displayed during testing, as the flow is being simulated to mimic a frictionless authentication experience.

Supported card test scenarios

✅ Success scenarios

Scenario	Test Card Number	CVC	Pin	Expiry Date	Notes
Valid Test Visa card	4242 4242 4242 4242	Any 3 digit	-	Any future date	You receive `12/35` as expiry date
Valid Test Master card	5555 5555 5555 4444	Any 3 digit	-	Any future date	You receive `12/35` as expiry date
Valid Test Verve card	5060 9900 0008 4242	Any 3 digit	Any 4 digit	Any future date	You receive `12/35` as expiry date

❌ Error scenarios

Scenario	Test Card Number	Error Code	Decline Code	Notes
The card was declined by the issuer for unknown reason.	5555 5568 7936 0005	`card_declined`	`do_not_honor`	You receive `12/35` as expiry date
The card does not have sufficient funds to complete the transaction.	5555 5515 3049 0051	`card_declined`	`insufficient_funds`	You receive `12/35` as expiry date
The card was reported stolen.	5555 5553 1674 0043	`card_declined`	`stolen_card`	You receive `12/35` as expiry date
The card used is not a test card.	xxxx xxxx xxxx xxxx	`invalid_test_card`	`N/A`	Not applicable

Regardless of the expiry details you send, payment_method_details.card.expiry always returns the fixed value 12/35 in every response and webhook payload while in test mode.

Testing first-in-series and next-in-series payments

Testing Cards

When testing card payments, always use test API keys. Only use the specified test cards listed below. Do not use real card information under any circumstances.

Note: The 3DS challenge page will not be displayed during testing, as the flow is being simulated to mimic a frictionless authentication experience.

In order to do an end-to-end first-in-series and next-in-series integration you can follow the below steps. Now you can use the same card number with different amount combinations to test different next-in-series scenarios.

First-in-series Test:

Make a first-in-series API request using the PS API.
Render the session_url on your client side and select cards.
Use the below card numbers and amount configurations to simulate the different scenarios.

Scenario	Outcome	Test Card Number	Amount (in minor units)	Expiry Date	cvv	Notes
The card needs to be authenticated and saved.	0$ Auth	5555 5555 5555 7777	0	Any date in the future	Any 3 digits	You receive `12/35` as expiry date
The card needs to be authenticated, saved and an initial charge needs to be processed.	Success scenario	5555 5555 5555 7777	Any amount	Any date in the future	Any 3 digits	You receive `12/35` as expiry date

Next-in-series Test:

Make a next-in-series API request using the PS API
Use the below amount configurations in the API to simulate the different scenarios, while passing the customer_id and payment_method_id in the API request.

Scenario	Outcome	Amount (in minor units)	Error Code	Decline Code	Notes
The card was declined by the issuer for unknown reason.	Error scenario	100000	`card_declined`	`do_not_honor`	You receive `12/35` as expiry date
The card does not have sufficient funds to complete the transaction.	Error scenario	200000	`card_declined`	`insufficient_funds`	You receive `12/35` as expiry date
The card was reported stolen.	Error scenario	300000	`card_declined`	`stolen_card`	You receive `12/35` as expiry date
Successful next-in-series card payment.	Success scenario	Any amount	`N/A`	`N/A`	Not applicable

Testing APM payment methods

Success and failure scenarios for APM (Alternative Payment Methods) payments can be simulated by initiating a payment with a specific amount. The amount should be specified in minor units.

Supported APM test scenarios

✅ Success scenarios

Test Amount	Webhook Fired
100001	Yes

❌ Error scenarios

Test Amount	Webhook Fired	Error Code
100002	Yes	`insufficient_funds`
xxxxxx	No	`invalid_test_amount`

Webhook Responses

Payment Session Update - When testing through the Payment Session API, an update will be triggered and delivered to your configured webhook endpoint via the payment_session.updated event.

Getting Started

Collect

Stored Value

Billing

Webhooks

Changelog

Overview

Testing Cards

Supported card test scenarios

Testing first-in-series and next-in-series payments

Testing Cards

First-in-series Test:

Next-in-series Test:

Testing APM payment methods

Supported APM test scenarios

Webhook Responses

​Overview

​Testing Cards

​Supported card test scenarios

​Testing first-in-series and next-in-series payments

​Testing Cards

​First-in-series Test:

​Next-in-series Test:

​Testing APM payment methods

​Supported APM test scenarios

​Webhook Responses

Overview

Testing Cards

Supported card test scenarios

Testing first-in-series and next-in-series payments

Testing Cards

First-in-series Test:

Next-in-series Test:

Testing APM payment methods

Supported APM test scenarios

Webhook Responses