Stripe v2 integration
- Trevor Vogt
Preparation
contact Stripe Support to complete necessary configuration for your Stripe account to accept requests from Zuora for 3DS2
contact Zuora Support to enable 3DS2 for your Zuora tenant (make sure Sandbox first)
configure new payment gateway instance with payment gateway type of Stripe v2
make sure the HPM instance being used is a v2.0 HPM:How to confirm if I'm using v2.0 HPM
make sure setting Enable 3D Secure 2.0 has been enabled for your HPM instance and correct payment gateway has been selected
make the necessary change to your code of HPM implementation
required change: "page id" of your HPM instance should be correctly specified
as a most basic test, there was no any other param change before/during my test except the page id
I've already got necessary change for CIT/MIT feature completed before this test, but if that has not been done in your HPM implementation, it will be another required change you need to have.
Test
access the page where your HPM instance is embedded and input the card data as usual
(test card number4000000000003220 has been used in my test)
Common Issue
error 400 [invalid_request_error/parameter_unknown] Received unknown parameter: payment_method_options[card][mit_exemption] happens when process a payment through Strip v2 with a payment method added through 3DS2 enabled HPM
this error means necessary settings on Stripe side has not been configured yet, please reach out to Stripe Support to further help.
error 402 -- [card_error/authentication_required/authentication_required] Your card was declined. This transaction requires authentication happens when processing a payment through Strip v2 with a payment method added through 3DS2 enabled HPM
when this error happens, it doesn't necessarily mean there is a problem in our integration.
Our integration will send required fields to the payment gateway and reflect the response we received into the payment status. But it is out of our control why response we will receive or if the payment transaction needs an authentication.
there is no authentication popup triggered
please confirm the description of the test card number being used in your test based on this document.
authentication behavior could be different when different test case numbers being used.