{"title":"Testing result codes and refusal reasons","category":"default","creationDate":1778684593,"content":"
\n
Test your in-person payments integration<\/h5>

See Simulating declined payments<\/a> to learn about triggering refusal reasons with an in-person payments integration.<\/p><\/div><\/div>\n\n

You can test how your integration can handle different responses to make sure your integration can handle failure scenarios. In such scenarios, you receive a result code and a refusal reason that tells you why a payment request did not succeed.<\/p>\n

You can trigger specific refusal reasons in your payment requests to test how your integration handles failure scenarios.<\/p>\n

Benefits of testing refusal reasons<\/h2>\n

This page describes how to trigger specific refusal reasons in your payment requests and test unhappy scenarios. There are several benefits to making sure your integration can handle unhappy flows, for example:<\/p>\n