Hi
We are developing an app for our client and want to integrate App Pay in our app through auth.net account. The client is a multi-location restaurant and each location already has it's own auth.net account set up.
However, when we publish this app to the app store, it will be under our developer's account not the client's developer account (as they don't want to pay developer fee&it's hard for us to manage). Question is, can we apply the merchant ID for each location in our apple developer account and use that to integrate into our app? By doing so would the transaction still go through client's auth.net account?
Thank you!
11-19-2021 01:39 PM
Integrating App Pay through Auth.net for a multi-location restaurant app is feasible, but there are some important considerations to keep in mind.
1. **Apple Developer Account:** Since you'll be publishing the app under your developer account, you won't be able to use the client's Auth.net account directly. The transactions will be processed through your Auth.net account instead of the client's.
2. **Merchant IDs for Each Location:** While you can apply for separate merchant IDs for each restaurant location under your Apple developer account, these IDs will be linked to your Auth.net account, not the client's. Each location will have its own merchant ID, but the transactions will be processed through your Auth.net account.
3. **Fees and Revenue:** If transactions are going through your Auth.net account, you'll be responsible for processing fees and handling revenue distribution to each restaurant location. You'll need to set up an agreement with the client on how these transactions and fees will be managed.
4. **Client's Auth.net Account:** If the client prefers to have transactions processed through their own Auth.net accounts for each location, they would need to publish the app under their developer account. In this case, you could assist them with the development and integration process.
5. **Legal and Contractual Agreements:** Ensure that you have clear legal agreements and contracts with the client regarding revenue sharing, transaction handling, and any other financial aspects related to the app.
6. **Data Security and Compliance:** As you'll be handling financial transactions, make sure to implement robust security measures to protect user data and comply with relevant regulations.
In summary, while it's technically possible to use separate merchant IDs under your developer account for each location, the transactions will go through your Auth.net account, and you'll have to manage revenue distribution and processing fees. If the client wants transactions to go through their own Auth.net accounts, they will need to publish the app under their developer account. It's essential to have a clear understanding and agreement with the client regarding these financial arrangements before proceeding with the development and integration of App Pay. For more here currentpackages
07-16-2023 01:16 AM - edited 07-16-2023 01:25 AM