Advertising sustains the DA. Ads are hidden for members. Join today

Contributed modules documentation

Payment

Payment is a fully pluggable and reusable platform for processing payments. Modules implementing it and payment methods are completely unaware of each other, which means that any module can use any payment method plugged into Payment and vice versa.
This handbook section describes the thoughts behind and the workflow of the Payment project, which is useful for site builders and developers.

For callback documentation, see the places where those callbacks are supposed to be configured, e.g. for the payment finish callback, which is Payment::finish_callback, see the declaration of that property in the Payment class definition.

Configuring "no payment required" payment methods

The ‘Basic Payment Method’ from Payment module is very versatile.

Debugging & exceptions

Payment offers its own PaymentException class that extends PHP's built-in exceptions.

Differences between Payment and Pay

Payment and Pay are both general payment processing platforms. It takes a different approach to be more light-weight and flexible than Pay

Payment execution workflow

Summary

Payment method installation & configuration

Payment methods for the Payment platform might require special installation and configuration.

Roadmap for 8.x-2.x

Showcases

This is a list of websites that use Payment to process payments of different types and amounts.

Terminology

The concept of a general payment platform

The concept behind Payment is that it prevents duplicate work ("reinventing the wheel") and that it improves quality, both because it tries

Writing a context

Writing a Payment context requires PHP knowledge.

Writing a payment method controller

A payment method controller (also known in the user interface as payment method type) is the logic for processing a payment using a

Guide maintainers

xano's picture