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

Create Customer profile using AcceptJS token #91

Open
appsierra-developer opened this issue Oct 31, 2017 · 2 comments
Open

Create Customer profile using AcceptJS token #91

appsierra-developer opened this issue Oct 31, 2017 · 2 comments

Comments

@appsierra-developer
Copy link

I am trying to make a purchase and creating customer profile using the transaction ID.
https://developer.authorize.net/api/reference/index.html#customer-profiles-create-a-customer-profile-from-a-transaction

I am able to purchase but I have no idea how to create customer profile using the transactionID. It seems possible only when I have a card.

purchase is made using AIM, but I am guessing I have to use CIM at same time for customer profile and transactionID seems the only thing that can bridge both.

@judgej
Copy link
Member

judgej commented Nov 1, 2017

I think @kotrakrishna was mostly involved in setting up the payment profile functionality a few years ago. It's not something I personally know a lot about.

However, if the search is working on github like I think it is, it does seem that there are request messages for creating customer profiles (i.e. payment profiles) e.g. CIMCreatePaymentProfileRequest and which are not actually used anywhere. That one does need a valid card though.

The Authorize.Net API is vast, and there are a lot of functions in it not covered by this driver. I have a feeling this is one of them. However, by actually using CIMCreatePaymentProfileRequest and modifying it so it so the valid card is not mandatory, supporting what you need may be relatively simple.

I do have the message data you need here and I fully intend to wrap that package into an Omnipay driver, but other priorities have put that on the sideline for the moment.

@judgej
Copy link
Member

judgej commented Dec 31, 2018

Does this PR fix this issue, or does it cover a different use-case?

#117

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

No branches or pull requests

2 participants