Closed fredtro closed 6 years ago
working with symfony 3 and ominpay is a huge problem. Omnipay v2 (which datatrans uses) is not compatible with symfony > 2. ominpay v3 is already in work, but still not finished....
sure, i've read about it on the omnipay page. My fault, i'm working on a symfony2 implementation.
so is this ready?
Not yet. I have finished "normal" cc payment process, next step is token billing. I will continue working on it end of this or next week. I can notify you when i am finished, if you like to.
yes please
Pls let me know if you will/will not accept my pull request, or if i have to improve, change or explain things. regards
I will merge it if it is an improvement for the library. Please continue and explain why and what you are doing, alright?
Ok, do you know what alias/token billing is?You can find infos here: https://www.datatrans.ch/alias-tokenization or Chapter 5 of https://admin.sandbox.datatrans.com/showcase/doc/Technical_Implementation_Guide.pdf.
Basically its about persisting credit card data as a token. Therefor you can use those 2 parameters from the pull request. By using "uppReturnMaskedCC=yes" you will receive a masked credit card number (like this 1234 *** 3424). Mostly persisted by client applications to show user in a user backend for example. Its more about displaying data, and not really mandatory for token billing.
By using useAlias=yes in a request, datatrans will persist credit card data for you (because in most cases its not PCI compliant to persist them as a merchant) and return a unique alias/token. This alias/token can be used for further transactions. In those cases user dont has to input CC data again.
Sounds good. Come back to me when this is finished, ok? :)
Thank you very much 🍻
Hi there
Me again 😀 I just need to request some additional data to implement Token billing.
Atm i am working on a Symfony 3 Bundle to use Datatrans in JMSPaymentCoreBundle. Sooo perhaps i will create some more pull requests in the future.
Cheers