You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 2, 2020. It is now read-only.
Good question. Looking back through the implementation, I don't see a trivial way to add it in a seamless way across all processors. Since the point of this library is to abstract your processor ... that'd be a good thing to do.
Authorize.net - It looks like we'd need to inject the order > invoiceNumber into the authorize/purchase requests.
IP Commerce - It looks like the IP Commerce implementation already allows you to pass an :order_id for it (so it's already supported, there).
NMI Customer Vault - We'd need to add an orderid query parameter to pass it through.
It seems likely that there's a good case for abstracting the local order identifier for a purchase onto the purchase attempts...
Is this still an issue for you, or was this just a question?
We worked around it by passing the orderid option around in our local copy of the code. We started using two different vault types but are just using one lately so it wasn't so hard to adapt. I do think it is very important to keep track of your payments orders or account ids so I think it would be great to have a standard way to set that up. I do want to thank you for the help in getting this project going though. It's been great for us.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
How do you include the order id in a purchase?
The text was updated successfully, but these errors were encountered: