Testing your integration
To avoid common pitfalls, we recommend that you test these scenarios, depending on the payment type you are integrating.
- For information about the API methods, see API methods for Merchant and Processor APIs.
- For information about the payment methods and providers, see Payment methods and providers.
- For information about the XML response, see API Response structure (XML).
The sections below contain links to pre-defined test data for triggering different scenarios.
General tests
Test these scenarios for each payment method.
Front end integration
-
Verify that the callback URLs have been set up in the API call. For backward compatibility reasons, you can also set them on the terminal, but this is not recommended.
- Verify that all requirements are met for the callback pages. For more information, see Setting up the callback pages. If the payment method uses the open page and/or the notification page, also ensure that these pages work as intended.
- Create a successful reservation using the createPaymentRequest method. For more information, see createPaymentRequest.
- If a payment fails, no further attempts should be offered.
- If there is a technical error, ensure that your customer is offered a second attempt, up to a maximum of 10 attempts.
Back end integration
- Capture a reservation using, for example, using the captureReservation method. For more information, see captureReservation.
- Release a reservation, for example, using the releaseReservation method. For more information, see releaseReservation.
- Refund a captured reservation, for example, using the refundCapturedResevation method. For more information, see refundCapturedReservation.
Recurring payment tests
These test cases are relevant if you want to do recurring payments.
- Setup a recurring payment using the createPaymentRequest or the setupSubscription method. For more information, see createPaymentRequest and setupSubscription.
- Capture a recurring payment using the captureReservation or chargeSubscription method. For more information, see captureReservation and chargeSubscription.
Fraud detection tests
- Ensure that customer data is sent correctly. Test using non-ASCII characters such as æ, ø, å to verify check-sum calculations using UTF-8.
- Ensure that the fraud risk score is being used or stored for later review.
- For test case data, see Credit card payments.
Token based credit card payment tests
Test these scenarios if you are accepting payments using credit card tokens.
- Ensure that the payment page (callback_form) is valid with javascript enabled
- Ensure that the payment page (callback_form) is valid with javascript disabled.
- For test case data, see Credit card payments.
Mobile Pay tests
- Ensure that there are no duplicate orders or errors on the OK page, because an order was already posted to the notification page URL.
- For test case data, see Mobile payments .