ePay · Bambora · Worldline
ePay integration (Bambora/Worldline) in a custom system
An ePay integration means your new system talks to the ePay, Bambora or Worldline agreement you already settle on — instead of cancelling a working acquiring setup because the shop changes technology. ePay is old in Danish webshop land. That is not an insult. It is an agreement, a merchant id and a set of callbacks bookkeeping already knows. Changing acquirer “while we rebuild anyway” is one of the most expensive unnecessary decisions we see. We keep the merchant agreement, change only the system that calls the API, and map old callback URLs to the new domain.
In the documentation we use the name your login still uses. In your UI we show what the customer knows: cards and maybe MobilePay. Payment layer.
ePay integration without moving the merchant number
- Keep the merchant agreement
- Change only the system that calls the API
- Map old callback URLs to the new domain
- Test 3-D Secure, refunds and partial capture before go-live
Keep ePay
- The agreement works, support answers
- Bookkeeping knows the settlement
- You do not lack MobilePay in week 1
Switch on purpose
- The agreement is expensive, or support is dead
- You lack MobilePay, which the new stack needs
- KYC time is a project of its own
When you should leave
If the agreement is expensive, support is dead, or you lack MobilePay that the new stack needs in week 1. Then the switch is a deliberate project with KYC time — not a footnote in another quote. QuickPay integration is the typical destination if you switch.
Callback URLs on the new domain
Old shops have callbacks on an expired domain or on /wp-admin. The new system needs those URLs before you cut the old shop. Test refunds and partial capture with real amounts in the test environment. Write the merchant id and the name the login still uses when you send the brief.
FAQ: ePay integration
Is it called ePay, Bambora or Worldline in the quote?
In the documentation: the name your login still uses. In your UI: what the customer knows (cards + maybe MobilePay).
Can we change shop without changing merchant number?
Yes. That is what we usually do. New technology, same agreement.
What if callbacks still point at WordPress?
Then you are not go-live. Map the URLs first. Otherwise paid orders land in a dead system.
Is ePay too old for a new system?
Old is not the same as dead. The agreement and the API decide. The login name beats the guess.