BridgePay is a payment technology provider that gives merchants a single connection to card processing, tokenization and reporting. If you run your Easy Digital Downloads store on WordPress, the BridgePay gateway plugin lets you take card payments without sending customers to a third-party site and without holding card data on your own server.
This guide walks through connecting BridgePay to Easy Digital Downloads, from the credentials you need through to testing and going live.
What you need before you start
- An active BridgePay merchant account, with access to your gateway credentials.
- A WordPress site running Easy Digital Downloads, kept up to date.
- A valid SSL certificate. Card payments must be collected over HTTPS, and most gateways refuse to process on an insecure connection.
- The BridgePay gateway plugin for Easy Digital Downloads.
If you do not have merchant credentials yet, request them from BridgePay before installing anything. Configuration cannot be completed without them, and a half-configured gateway can leave a broken payment option visible to customers.
Step 1: Install the plugin
Download the plugin, then in WordPress go to Plugins → Add New → Upload Plugin, choose the ZIP file and activate it. A new BridgePay section appears in your Easy Digital Downloads payment settings once activation completes.
Install on a staging copy first if you have one. Payment changes are one of the few areas where a small mistake is immediately visible to customers.
Step 2: Enter your merchant credentials
Open the BridgePay settings and paste in the credentials from your merchant account. Keep test and live credentials separate and clearly labelled, because the two sets look similar and it is easy to leave test keys in place after launch.
Never paste credentials into a support ticket, a shared document or a public forum. Anyone holding them can process transactions against your account.
Step 3: Configure how the gateway appears
Set the title customers see at the Easy Digital Downloads checkout. Something plain such as “Credit or debit card” converts better than a processor name most shoppers will not recognize. Add a short description if the payment options need explaining.
Decide which card brands to accept and whether to capture payment immediately or authorize first and capture on fulfilment. Authorize-then-capture suits businesses that ship physical goods; immediate capture suits digital delivery.
Step 4: Test before you take real money
Switch the gateway into test mode and run through the Easy Digital Downloads checkout as a customer would. Check each of these:
- A successful payment completes and the order or entry is recorded correctly.
- A declined card shows a clear message rather than a blank page or a raw error code.
- Confirmation emails reach both you and the customer.
- The amount charged matches the amount shown, including tax and any fees.
Test a decline deliberately. Most payment problems reported after launch are not failed charges but confusing messages when a card is refused.
Step 5: Go live
Swap the test credentials for live ones, turn test mode off, and make one real payment with your own card. Refund it immediately. That single transaction confirms the whole chain works, from the Easy Digital Downloads checkout through to funds reaching your account.
Refunds and failed payments
Process refunds from within WordPress where the plugin supports it, so your records and the gateway stay in step. Refunding directly in the BridgePay portal leaves the WordPress record showing the original amount.
For failed payments, check the gateway response first. A decline is a decision by the customer bank and cannot be overridden. A gateway error usually points to credentials, a currency mismatch or an expired certificate.
Troubleshooting
The gateway does not appear at checkout. Confirm the plugin is active, the gateway is enabled, and any currency or country restrictions match the order being placed.
Every transaction is declined in test mode. Live credentials are often the cause. Test credentials only work against the test endpoint.
Payments succeed but orders stay unpaid. The gateway response is not reaching your site. Check that your host is not blocking the callback and that no security plugin is filtering it.
Getting the plugin
The BridgePay Payment Gateway for Easy Digital Downloads is available from wpayo, with updates and support included. Once installed, the setup above takes most sites under half an hour.
Is BridgePay the right choice for your site?
BridgePay suits merchants who want card processing handled on their own checkout rather than on a redirect, and who value tokenization so returning customers do not re-enter card details. It is a reasonable fit if you already hold a merchant account, or want one acquirer relationship across several sales channels.
It is less of a fit if you want to be taking payments within ten minutes of signing up and have no merchant account yet. Instant-onboarding providers trade lower setup effort for higher per-transaction cost and a greater chance of an abrupt account hold. Which trade-off suits you depends on volume: at low volume the convenience usually wins, and at higher volume the rate difference starts to matter more than the setup time.
Security and compliance
Keeping card data off your own server is the single biggest reduction in PCI scope you can make. A gateway integration that tokenizes the card means your database stores a reference, not a number, so a site compromise does not expose card details.
That does not remove your obligations entirely. You still need HTTPS across the site, current WordPress and plugin versions, strong administrator passwords with two-factor authentication, and restraint about who holds an admin account. Most breaches on WordPress sites begin with an outdated plugin or a reused password, not with the payment gateway.
Frequently asked questions
Do customers leave my site to pay?
No. The gateway is designed to keep the payment step on your own checkout, which generally converts better than a redirect because shoppers are not handed off to an unfamiliar page mid-purchase.
Can I take recurring payments?
Tokenization is what makes repeat billing possible, since you charge a stored token rather than asking for the card again. Whether recurring billing is available depends on your Easy Digital Downloads setup and the subscription extension you use, so confirm both before promising customers a subscription option.
What happens if a payment is disputed?
A chargeback is raised by the cardholder bank and you get a window to respond with evidence. Keep order records, delivery confirmation and the authorization response. Sites that cannot produce evidence quickly lose disputes they would otherwise win.
Will this slow my checkout down?
The gateway call adds a round trip measured in fractions of a second. If your checkout feels slow, the cause is almost always page weight, hosting or plugin bloat rather than the payment request itself.
Leave a Reply