-
Notifications
You must be signed in to change notification settings - Fork 35
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
Comments
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. |
This is for the Payeezy gateway which does support transarmor tokens. |
Noted, I have some Payeezy test credentials, I'll take a look, unless you want to submit a PR yourself. |
@delatbabel I am working on adding tokenization support as we need it in our system. 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: Before I make the official PR, I will squash my comments to reduce the noise. |
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. |
I believe this is still open, waiting for a PR. |
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. |
Well I did my best |
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.
The text was updated successfully, but these errors were encountered: