WBAMS ships 20 payment gateways: Stripe, Stripe ACH, Stripe SEPA and Stripe Dynamic Payments; PayPal, Credit/Debit Card (PayPal), PayPal Basic, PayPal Website Payments Pro, PayPal Pro Reference Payments and Payflow Pro; Authorize.net, Authorize.net CIM and Authorize.net Echeck; Helcim, Payment Express, PayJunction and Payments Gateway; and Bank Transfer and Mail In Payment. They differ in their credentials but the setup is the same shape every time, and the step people skip — the callback — is the one that decides whether payments are recorded.
Activate the gateway
- Open Settings → Payment Gateways.
- Find the provider in the list of available gateways and activate it.
- Fill in the credentials the provider gave you. Most gateways have a test or sandbox mode — use it first.
- Set the display name customers will see at checkout. This is customer-facing wording, not the module name.
- Choose which currencies the gateway accepts, if it does not accept all of yours.
- Save.
Before 1.12.0 WBAMS shipped 67 gateways. An upgrade leaves the files of one it no longer includes where they are and lists them on its result page, but WBAMS no longer loads them. A site that takes payments through one should set up one of the gateways above in its place, best before it upgrades, so clients can always pay; then delete the old files.
Where a gateway is offered
The Content Manager’s Checkout › Payment rules (the Payment Gateway Wizard) limits a gateway to some countries, keeps it from others, or gives it a smallest and largest amount, in the site’s default currency. Since 1.12.0 the rules are applied wherever a client chooses how to pay: the list at checkout, the order’s own check, and the payment methods on an invoice. A gateway with rules is offered when one of them allows it; a gateway with none is offered everywhere. A country or amount that is not known yet, such as a visitor who has not given an address, is not held against a rule. Before 1.12.0 the rules were saved and never applied.
Register the callback
A gateway tells WBAMS that a payment succeeded by calling back to your site. If the callback is not registered, or is registered at the wrong address, the customer pays and the invoice stays unpaid.
The callback address follows one pattern:
https://example.org/extensions/processors/callback/GATEWAY.php
Replace example.org with your System URL and GATEWAY with the module name — stripe.php, helcim.php, and so on.
Stripe, for example, creates its own webhook against your System URL when you save valid credentials. Others require you to paste the address into the provider’s dashboard. Check the provider rather than assuming.
The callbacks live at the provider, pointing at the old address. Moving domain or switching to HTTPS means re-registering every gateway.
Test with a real payment
- Put the gateway in test mode and place an order as a customer, in a private window.
- Pay with the provider’s test card or sandbox account.
- Confirm you return to the client area and the invoice shows as paid. This is the test that matters — a successful payment at the provider that leaves the invoice unpaid means the callback did not arrive.
- Check Platform → Gateway log for the callback as received.
- Check the transaction was recorded against the invoice with the right amount and fee.
- Switch to live mode and repeat with a small real payment, then refund it.
When a payment does not land
- Read Platform → Gateway log first. If there is no entry, the callback never arrived — the problem is the registered address, not WBAMS.
- If there is an entry, read Platform → Module log for what the module did with it.
- Confirm the System URL in Settings → General matches the address the provider is calling.
- Check the provider’s own dashboard for delivery attempts and their responses. A 404 or 500 recorded there points straight at the cause.
It hides the broken callback, and the next payment fails the same way. Fix the callback and let it settle properly.
Settings a particular gateway adds
Most of the setup above is the same whichever gateway you activate. One setting is specific enough to be worth spelling out, because the module links to this page from beside it.
Stripe: Allow Payment Request Buttons
Off by default. Turn it on and a supported browser offers the card the visitor already has stored — Apple Pay on Safari, Google Pay on Chrome — as a single button above the card fields on the invoice payment page. Nothing changes for a visitor whose browser has no stored card; they see the ordinary form.
Two conditions have to hold before the button appears at all, and neither is set in WBAMS:
- The page must be served over HTTPS. The button is hidden on a plain HTTP page.
- Your domain must be registered with Stripe under Settings → Payments → Payment method domains, which is where Apple requires the domain association file to be verified.
If the setting is on and the button still does not show, test in a browser that has a card saved and check the domain registration first — that is the usual cause.
Offline payment methods
Bank transfer, check and other manual methods need no gateway. Record them from the invoice with Add payment, or from Billing → Offline payment for a batch.