TruPayments Overview

TruPayments is the shared payment layer that Booking and TruCommerce use to offer payment methods and keep transaction/refund history in one place.

TruPayments centralizes payment activity used by enabled modules such as Booking and TruCommerce.

What this feature is for

TruPayments is the shared payment layer used by other TruCMS modules. Booking and TruCommerce decide what the customer is paying for; TruPayments decides which payment methods are available, sends online payments to the selected gateway, records transactions and keeps their status/history together.

Booking / TruCommerce TruPayments payment method Gateway or manual method Transaction & history

This separation is important when troubleshooting. If an order or appointment total is wrong, investigate the owning module. If the correct total reaches checkout but a payment choice is missing or a gateway fails, investigate TruPayments and the gateway configuration.

A practical way to use it

1. Choose the default payment currency and confirm the public payment prefix.
2. Configure any gateway add-ons you intend to use in sandbox/test mode first.
3. Create or edit Payment Methods to decide which choices customers can actually see.
4. Use Billing Zones when a method should be limited to specific billing countries/provinces.
5. Run a real module checkout in test mode and confirm the resulting Transaction and history before enabling live credentials.

How it connects to other features

Gateway add-ons supply gateway capability and credentials, but Payment Methods control customer-facing availability. Booking and TruCommerce supply the payable amount and business context. Billing Zones can further restrict a payment method by billing address.

What to expect after changes

Changing payment configuration can affect every module that uses TruPayments. Test changes with Booking and TruCommerce separately because each module can apply its own checkout rules before TruPayments is called.

How the pieces fit together

Connected module (Booking or TruCommerce) chooses the amount/currency → TruPayments determines eligible customer-facing Payment Methods → the selected gateway add-on processes the payment when it is an online gateway → TruPayments records the resulting transaction and refund history.

Recommended setup order

1. Review TruPayments Settings and choose the default currency used when a connected module does not provide one.
2. Install/activate and configure the required gateway add-on: PayPal, Stripe, Mollie, or Braintree.
3. Create Billing Zones only when a payment choice should be limited by the payer’s billing country/province.
4. Create or edit the customer-facing Payment Method. Set its gateway, scope, currencies, Billing Zones, order, and Enabled state.
5. Test the method through the Booking or TruCommerce checkout that will actually use it.
6. Use Transactions for payment/refund history and reconciliation after launch.

Gateway vs. Payment Method

A gateway is the processing capability/credentials. A Payment Method is the choice customers see and the rules that decide where it can appear. Configuring a Stripe API key does not automatically make “Stripe” available at every checkout; the corresponding Payment Method must also be enabled and eligible.

Day-to-day administration

Payment problems

If a payment method does not appear at checkout, a payment stays pending, or a refund fails, work through the cause-by-cause answers in the Payments FAQ.