Skip to main content
Some payment methods, such as bank transfers, do not return to the server after completion. These methods, termed “Push Payments,” involve presenting the user with payment details (like a QR code), after which there is no return to the merchant page. The transaction is an open order, with the payment being pushed to the order asynchronously by the buyer.

​
API usage

All push payment transactions use the mode value of redirect, but where a normal redirect payment returns with a status of buyer_approval_pending, a push payment moves directly to the processing status. If doing a direct integration, link the transaction ID to the order, and then either redirect the user to the approval_url on the transaction, or present that same URL in a popup or <iframe> if possible.

​
Webhooks

As the buyer is unlikely to return to the redirect_url afterwards, set up webhooks between the payment service and the server to be notified of the completion of the transaction. Additionally, set up webhooks between the system and yours to be notified of the completion of the transaction as well.