-
Notifications
You must be signed in to change notification settings - Fork 78
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
Please share an example of how to reuse token for a monthly subscription payment. I can't find out in docs. #152
Comments
There is some documentation on card tokens here: https://github.com/thephpleague/omnipay-sagepay#token-billing SagePay does not provide a regular billing schedule. Instead, you get a |
Hi judge, thanks for the reply to me. "https://github.com/thephpleague/omnipay-sagepay#token-billing" |
I'll try to get something together over the next few days. In the middle of an office move at the moment. |
Yikes. Lockdown during that office move meant we never actually moved, and things got complicated. I've added examples to my ever-growing list. But if you have found your way to the solution anyway, then any examples of how you did it will be very useful. |
I'm guessing the office move is still off.... On this issue though - I'm setting createToken and I can see that the url ends in &CreateToken=1 as a result However, it appears that the response should include Token as a field - which is does not. My current theory is that it is because the account has not been enabled for tokens per https://developer.sage.com/api/payments/additional-integrations/tokens/#:~:text=card%20identifiers%20(Tokens)-,Overview,proceed%20to%20the%20checkout%20pages. However, I also note that that page does not mention the option of passing createToken and I can't find much mention on their site so it's also possible it's something they are phasing out? |
Please share an example of how to reuse token for a monthly subscription payment.
I can't find out in docs.
please help me
The text was updated successfully, but these errors were encountered: