Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Authorize.net shows E00040 when Creating Subscription from Customer Profile #78

Open
sarathrj10 opened this issue May 12, 2021 · 2 comments

Comments

@sarathrj10
Copy link

I am creating an ARB Subscription in Authorize.net using the customer profile. This is my flow :

  1. creating a customer and payment profile.
  2. create the first-month payment through auth capture.
  3. creating an ARB subscription using this customer profile.

Here 1 & 2 completes successfully but the 3rd step shows the error: E00040, The record cannot be found. This error occurs only when I am creating the subscription just after creating a new profile. If I use this same customer profile to create the ARB subscription after some time, it works fine. It will be very useful if anyone could help me out in this scenario. Thanks in Advance.

@GodAlmighty990
Copy link

The PRoblem is you HAVE to WAIT like 15 seconds to one minute from creating a customer payment profile and then creating a subscription with it. Take their card info, run your request to create customer payment profile, once that comes back take the response (if successsful) and make your post request to your backend to create the subscription but use a setTimeout(() => {}, 15000) or something.

Its a ridiculous error but you can have modal pop up that says, "creating your account" or something and if your card info comes back bad after waiting 15 seconds or 30 seconds, ("ive not issues with 15 seconds but docs say to wait one minute"), then just show customer something saying there was an error with their card

@saikumarkale
Copy link

TCS-Dev saikumarkale- The error occurs due to sending back-to-back requests, it will take some time to replicate the data, to overcome this issue we should add some waiting time in between one request to other request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants