Solved! Go to Solution.
08-21-2018 11:30 AM
Got the localhost thing solved. Look into ngrok for those needing the same thing.
But after digging in, I don't believe Shared CIM will solve our problem.
Scenario: We have one customer that registers at one store and we add thier customer profile to one Auth.Net account. If they go to another store (same business) with a different Auth.Net account we did not want the customer to have to create a separate customer profile. It sounded like Shared CIM could have solved this but with the OAUTH layer it really does not not because it is the customer on the web app not the business owner.
Does Authorize.Net have a solution or any suggestions for this?
Thanks, Jay.
07-26-2019 01:06 PM
I also am interesting in this functionality for a fairly large client that has about 50 locations with 50 separate Merchant IDs.
02-10-2020 01:58 PM
Hello @Anurag , I am looking for the exact same functionality where I can make customer profile only once throughout the app and multiple merchants can access those already created customer profile.
10-14-2020 08:32 PM
We found that Shared CIM will not work for us. I have also seen a couple other posts on this thread with a similar need to share a customer profile accross accounts.
Just wanted to check and see if Authorize.Net has any other options for this in the pipeline other than Shared CIM OAUTH route.
01-28-2021 05:47 AM
I likewise am fascinating in this usefulness for a genuinely Massager Consult huge customer that has around 50 areas with 50 separate Merchant IDs.
02-06-2021 12:08 AM
@Anurag Is the invitation to join the preview still available or has that feature been abandoned?
11-03-2021 02:26 PM
Facing challenges sharing a credit card across multiple merchant accounts? Ensure secure and compliant transactions with proper UAE embassy attestation.
11-07-2023 10:09 AM