Testing Recurring Payments

Recurring Payments

When integrating recurring payments, it’s essential to test a variety of scenarios to ensure the system can handle different decline responses effectively. Use the following amounts to simulate specific payment failures, allowing you to verify how your integration manages these cases and provides accurate feedback to customers.

Here are the test amounts and their corresponding status and reason:

AmountStatusReason
101declinedgeneric_decline
216declinedinvalid_avs
217declinedinvalid_pin
218declinedclosed_account
251declinedsuspected_fraud
301declinedinsufficient_funds
321declinedcardholder_cancellation
323declinedrestricted_card
324declinedinvalid_cvv
325declinedexpired_card
402declinedlost_or_stolen

Apple Pay Recurring

To test Apple Pay recurring set the amount to 28.29 to produce a successful response.