TruPayments Settings

Set the payment defaults that connected modules use when they create a transaction.

TruPayments settings page

Configure shared payment behavior before relying on payment methods from Booking or TruCommerce.

What this feature is for

These are the shared defaults for TruPayments itself. They are intentionally documented inside the TruPayments section because their effect is cross-module: Booking and TruCommerce can both create transactions through the same payment layer.

The Default Currency is the fallback currency for payment activity when the calling workflow does not supply another supported currency. The Front Prefix controls the public URL segment used by TruPayments screens; changing it is an address/URL decision, not a display-label change.

A practical way to use it

  1. Choose the currency your payment setup should use as the shared default.
  2. Set the public payment prefix once before launch and avoid unnecessary later changes.
  3. Configure each gateway add-on separately.
  4. Create/enable the Payment Methods that expose those gateways to customers.
  5. Perform test transactions from the modules that will use payments.

How it connects to other features

Gateway credentials do not live on this general TruPayments page; each gateway add-on has its own settings. Customer-visible method availability is controlled by Payment Methods and optional Billing Zones.

What to expect after changes

A default-currency change can affect newly created payment flows that rely on the default. A Front Prefix change changes TruPayments public URLs and can invalidate old bookmarks or externally stored links.

Settings

SettingWhat it controlsGuidance / effect
Default CurrencyThe three-letter currency used when a connected module creates a payment without explicitly supplying one.Use the main currency your installation expects to transact in. Booking or TruCommerce can still pass their own currency for a specific payment when their workflow supports it.
Payment URL PrefixThe frontend URL segment used for TruPayments hosted payment pages and callbacks.Treat this as a routing/branding setting. Changing it changes the public path used by payment pages, so do not change it casually on a live site with payment links in progress.
  1. Install and activate TruPayments and the gateway add-on you intend to use.
  2. Configure the gateway add-on credentials and test/live mode.
  3. Set the TruPayments default currency here.
  4. Create Billing Zones only when a method must be limited geographically.
  5. Create/enable the Payment Method that customers will see, then test it from Booking or TruCommerce checkout.

Payment Methods · Billing Zones · Transactions · Stripe