---
title: 'The Payment Process'
url: 'https://manuals.remository.com/payage/overview/the-payment-process'
markdown: 'https://manuals.remository.com/payage/overview/the-payment-process.md'
date: '2026-11-14'
description: 'Payage creates "Buy Now" buttons that handle payment in conjunction with an external payment gateway. When an application is ready to receive payment, it requests payment buttons from Payage. The application then displays the button(s) returned on its payment page. A button is returned for each pub…'
taxonomy:
  category:
    - docs
---

[](#) [ edit this page](https://github.com/getgrav/grav-skeleton-rtfm-site/blob/develop/pages/03.overview/01.the-payment-process/docs.md) 

# The Payment Process

Payage creates "Buy Now" buttons that handle payment in conjunction with an external payment gateway.

When an application is ready to receive payment, it requests payment buttons from Payage. The application then displays the button(s) returned on its payment page. A button is returned for each published account that matches the requested account group and currency. There are lots of button and layout options.

![](https://manuals.remository.com/payage/user/pages/03.overview/01.the-payment-process/p-8_1.jpg)

One of the goals of Payage is to enable payment solutions in such a way that your site does not need to comply with the requirements of the Payment Card Industry Data Security Standard, since that is very difficult for small businesses to achieve. Different payment gateways have different solutions to this. Some gateways redirect the user to the gateway site for payment and return the user to your site after payment. Some solutions allow the user to remain on your site through the entire process. Payage handles both kinds.

When the customer has paid, Payage performs exhaustive verification checks with the gateway to ensure that the customer has paid the correct amount in the correct currency, and then returns control back to the calling application. The application avoids any gateway-specific processing, and Payage avoids any application-specific processing.

 [ ](https://manuals.remository.com/payage/overview) [](https://manuals.remository.com/payage/overview/payage-is-invisible-to-end-users)

---

## Navigation

- Parent: [Overview](https://manuals.remository.com/payage/overview.md)
- Next: [Payage is Invisible to End Users](https://manuals.remository.com/payage/overview/payage-is-invisible-to-end-users.md)