Why does the payment user interface keep redirecting to a nested iframe?

After capturing user payment data in your user interface, you must redirect to the shopperResultUrl using the partner-redirect event. This forces the outermost iframe to redirect correctly.

For more information, see the Checkout plugins integration guidelines.

Why doesn't the Peach Payments Checkout loader go away after selecting the payment method?

• You are not sending Checkout the expected events to indicate that your user interface has finished loading.
• The origin URL that Peach Payments is expecting is different from the origin URL that the redirect URL sent in the debit response.

Why am I not receiving requests from the Partner API?

Your API might be timing out.

Why is the debit response failing validation due to the redirect URL?

The redirect URL should be URL-encoded to pass Peach Payments Partner API validation.

How does cancel functionality work and what cancel result code should I use?

If the user abandons the transaction by clicking an element such as an “X”, Peach Payments expects the "cancelled by user" result code in a webhook. This differs from the implementation of a cancel endpoint and cancel functionality which is optional.

When should I send webhooks?

• Every time the transaction changes status.
• Every time a transaction is created, Peach Payments expects a webhook with a 000.200.000 result code.

When should customParamaters be echoed back?

The customParameters object should be echoed in the response to every request, including webhooks. Different requests have a different number of customParameters, so we suggest treating it as a dynamic object and returning that object.