Closed qooplmao closed 1 year ago
No problem on making the PR. A guy working on our project made a fork with this change initially. We only used it to build a create a charge and we store all of the data elsewhere so refactored things so the additional dependency wasn't necessary but I this might be worth pushing back up.
Can you rebase your changes off of master? There was a glitch with autoloading and github actions
It should be good now. I'm doing this all through the GitHub site because I'm being too lazy to clone it on my local so sorry if I'm missing something.
3D Secure (Strong Customer Authentication, or SCA, in the EEA) requires a verification token that is generated on the frontend be sent with the charge.
This just adds the
verification_token
to the$prepData
(null if not present) and then sets it in theCreatePaymentRequest
.In addition the Simple Example could be updated to