---
title: 'Payment Gateway Returns'
url: 'https://manuals.remository.com/payage-dev/how-payage-works/payment-gateway-returns'
markdown: 'https://manuals.remository.com/payage-dev/how-payage-works/payment-gateway-returns.md'
date: '2026-11-14'
description: 'Without Payage, applications would specify a return URL to the payment gateway that redirects the user back to the application. When Payage generates payment buttons, it specifies the payment return URL as the front end of Payage. Payage then handles all of the gateway-specific payment verification…'
taxonomy:
  category:
    - docs
---

[](#) [ edit this page](https://github.com/getgrav/grav-skeleton-rtfm-site/blob/develop/pages/03.how-payage-works/02.payment-gateway-returns/docs.md) 

# Payment Gateway Returns

Without Payage, applications would specify a return URL to the payment gateway that redirects the user back to the application. When Payage generates payment buttons, it specifies the payment return URL as the front end of Payage. Payage then handles all of the gateway-specific payment verification procedures, and then redirects back to the application. The user is not aware of this.

Many gateways also have the ability to call a URL for subsequent updates such as refunds. These are also handled by Payage first, which performs verification, updates its payment record, and then calls the application. This callback is a PHP function because in this case the "client" is not a browser, it is a program at the payment gateway which may or may not support redirection.

 [ ](https://manuals.remository.com/payage-dev/how-payage-works/the-payage-database-tables) [](https://manuals.remository.com/payage-dev/receiving-payments)

---

## Navigation

- Parent: [How Payage Works](https://manuals.remository.com/payage-dev/how-payage-works.md)
- Previous: [The Payage Database Tables](https://manuals.remository.com/payage-dev/how-payage-works/the-payage-database-tables.md)