TruPayments Payment Methods

Decide which payment choices customers can see, where they can use them, and which gateway processes them.

TruPayments payment methods list

Payment Methods is where administrators control which configured ways of paying are available to modules.

What this feature is for

Payment Methods are the customer-facing payment choices. A gateway add-on such as Stripe gives TruPayments the ability to talk to Stripe; the Payment Method decides whether that capability is exposed as an available checkout choice, with its own name, ordering, status and restrictions.

This is the page to use when a configured gateway exists but customers cannot see it—or when you need to make the same gateway available only in a specific context/geography.

A practical way to use it

  1. Configure the underlying gateway add-on or manual method first.
  2. Create/edit the Payment Method and choose the gateway it should use.
  3. Set its customer-facing label, active state/order and any supported currency/context restrictions.
  4. Assign Billing Zones when billing geography should limit the method.
  5. Test the method from each module that should use it and confirm a Transaction is created.

How it connects to other features

Gateway settings provide credentials. Billing Zones can restrict availability by billing address. Booking and TruCommerce request the available methods for their own checkout context, so the same payment method can participate in more than one module.

What to expect after changes

Disabling a method removes it as a new checkout option without rewriting historical transactions. Changing restrictions affects future method selection; existing transaction history remains tied to the method/gateway that processed it.

Gateway vs. Payment Method

A gateway is the payment capability and credentials—such as Stripe, PayPal, Mollie or Braintree. A Payment Method is the choice shown to the customer and contains presentation/availability rules. Keeping these separate lets you configure one provider, then control how it is offered to Booking or TruCommerce customers.

What makes a method available

RuleEffect
EnabledDisabled methods are not offered for new checkout selections, while historical transactions remain.
GatewayThe selected gateway must be installed/configured and ready to process the method.
ScopeLimits the method to the module/context selected by the method, such as Booking, TruCommerce or a broader scope when available.
Supported currenciesThe checkout currency must be one the method/gateway supports.
Billing ZonesWhen selected, the payer’s billing address must match at least one assigned Billing Zone. Leaving the selection empty means no billing-zone restriction.
Position / sortingControls the order in which eligible methods are presented.
  1. Configure and test the gateway add-on that will process the payment.
  2. Create or edit the customer-facing Payment Method and choose its gateway.
  3. Set its scope, supported currencies and optional Billing Zones.
  4. Enable the method and place it in the order you want customers to see.
  5. Test from the relevant Booking or TruCommerce checkout using an address/currency the method should support.

Disabling is safer than deleting during troubleshooting

If a method should temporarily stop accepting new payments, disable it first. Existing transaction history remains useful for reconciliation.

Billing Zones · Transactions · PayPal · Stripe