-
Notifications
You must be signed in to change notification settings - Fork 5
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
Apple Pay Amount 'null' #9
Comments
Are you running on a physical device? I know Apple Pay doesn't work in simulator and you also need to use Apple Pay Sandbox on your device. If you are running on device with Apple Pay Sandbox already, run via XCode and check the debug console logs. If you are still having problems you could check if v1.0.0 of this package works, I think I last tested Apple Pay somewhere around that version. |
Can confirm, it still does not work on device with sandbox. However, doing sandbox on device does provide the -- Edit By hardcoding the amount in my fake api for make-payment apple pay transactions do go through. Going to take a look at figuring out why the amount value just gets nulled when using apple pay |
V1.0.0 yields the same result, still working on tracing why the amount gets nulled. Not too versed in swift so it's not the funnest time :) |
@domtalbot Hey, if you still need a solution there is a new version v3.0.0 available now which I have confirmed Apple Pay works in. Migration instructions |
Thanks for coming back, i did manage to get it working but with some questionable Swift coding. This will be useful. |
I'm trying to add ApplePay to my proof of concept, having issues with their not being an amount passed through on the
make-payment
request. I've scoured through the files to confirm that the amount is being set in config as requested but still it passes through as null.Confirmed that the standard card integration is still passing through the amount and payments go through fine. It's just apple pay being a pain. Do you have any ideas?
Config:
Generated request:
Response:
The text was updated successfully, but these errors were encountered: