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

Transarmor tokenization transaction #9

Closed
jwahl opened this issue Jan 26, 2016 · 8 comments · Fixed by #14
Closed

Transarmor tokenization transaction #9

jwahl opened this issue Jan 26, 2016 · 8 comments · Fixed by #14

Comments

@jwahl
Copy link

jwahl commented Jan 26, 2016

There appears to be no way to submit a transarmor tokenization transaction in the library. I can create a token by submitting a $0 pre-auth and receive it back just fine but I see no way of using that token to complete a transaction. Am I missing something? There is basically nothing on StackOverflow about this.

@delatbabel
Copy link
Contributor

Which of the gateways are you referring to?

For the Webservice gateway I don't believe that it supports transarmour tokens.

For the Payeezy gateway I believe that it does support transarmour tokens but I haven't gotten around to implementing it yet. If you want to submit a PR then go ahead.

For the Connect 2.0 gateway I think it supports transarmour tokens but I haven't been able to obtain test keys (see #8) so I'm not able to implement and test it.

@jwahl
Copy link
Author

jwahl commented Jan 27, 2016

This is for the Payeezy gateway which does support transarmor tokens.

@delatbabel
Copy link
Contributor

Noted, I have some Payeezy test credentials, I'll take a look, unless you want to submit a PR yourself.

@dmregister
Copy link
Contributor

@delatbabel I am working on adding tokenization support as we need it in our system.
It also adds support for ACH purchases as well. Here is the compare:

master...dmregister:master

One of my concerns is adding public methods to the library, I feel the abstract is getting a bit leaky. Just wanting to get your thoughts on what direction you had in mind.

My initial approach was to integrate directly with the api, but that was getting too complicated for this library:

dmregister@915c089

Before I make the official PR, I will squash my comments to reduce the noise.

@atraianovschi
Copy link

atraianovschi commented Nov 22, 2016

Is this issue still opened ? Any updates on this ? I also need the tokenized transactions for Payeezy gateway and is very important.

@dmregister your changes are for a different gateway and it has nothing to do with FirstData. There are 2 different APIs and they can't be combined because they have different configurations and you need different merchant accounts for each of them and you can't combine them.

@delatbabel
Copy link
Contributor

I believe this is still open, waiting for a PR.

@RickKukiela
Copy link
Contributor

This is unbelievable. What is the point of tokenizing a card if you aren't going to re-use it? I thought this module could be trusted as complete since its part of the "by omnipay" family of plugins....

Uggghhhh Now I have to do a PR to add functionality to a library that should already have it, that I really know nothing about the internal workings of, when the original developer could have added a provision for this in a fraction of the time its going to take me. Fantastic.

For the record I'm referring to the FirstData_Payeezy gateway. I've tokenized cards, stored the token and now I want the user to be able to make charges using the stored token.

@RickKukiela
Copy link
Contributor

Well I did my best
#14

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

Successfully merging a pull request may close this issue.

5 participants