Implementing multiple payment gateways on same domain

Question

Created 3d

Replies 1

Boosts 0

Participants 2

Hi Everyone,

My team is working on an online marketplace for FMBs in Saudi Arabia (with a plan to expand to other markets later). We are currently working on integrating multiple payment gateways with embedded Apple Pay support into our platform.

We’ve encountered an issue with the apple-developer-merchantid-domain-association file. Based on advice from one of our payment partners, we've ensured that the domain association file is uploaded in the correct format. This works successfully with our first payment gateway.

However, for the additional payment gateways we are integrating, we would also like to enable Apple Pay with embedded support. The challenge is that each payment gateway requires its own domain verification, but the verification file uses the same file name. This prevents us from supporting multiple gateways on the same domain.

Has anyone in the house been able to implement a similar solution, or know how we can best implement this?

Please, I'll appreciate advise on how we can configure Apple Pay domain verification to support multiple payment gateways on the same domain? Any specific guidance or best practices would be greatly appreciated.

Best regards,

Boost

Answer 1

by_ptr OP

2d

That could be a little problematic to have all gateways in the same domain because as far as I understand, Apple provides the domain verification files per platform integrator, so the gateway that provided you with the verification file is your integrator. And I am not sure how Apple treats multi-integrator platforms.

Is it possible for you to register as a merchant, decrypt the payload as a merchant and then send the transaction to gateways for authorization? That might be a better solution.

0