Closed dmitrii-fediuk closed 7 years ago
It is because the derived single-use 3D Secure source has redirect/status
: not_required
:
"redirect": {
"failure_reason": null,
"return_url": "https://mage2.pro/sandbox/dfe-stripe/customerReturn",
"status": "not_required",
"url": "https://hooks.stripe.com/redirect/authenticate/src_1BNt5rFzKb8aMux1wrGBra5u?client_secret=src_client_secret_BlPvYxsByORoyQ43jLY8LCdI"
},
The Stripe API Reference says:
status string | The status of the redirect, either `pending` (ready to be used by your customer to authenticate the transaction), `succeeded` (succesful authentication, cannot be reused) or `not_required` (redirect should not be used) or `failed` (failed authentication, cannot be reused). |
stripe.com/docs/api#source_object-redirect-status
It looks like the phrase «should not be used» is incorrect here, and we can use the 3D Secure verification, because it is optionally supported by the bank card: three_d_secure
: optional
(see the initial source).
I tried to enforce the 3D Secure verification when redirect/status
is not_required
(redirect the customer to the redirect/url
), but Stripe did not allow it: it just redirected the customer back to the redirect/return_url
.
So the phrase «should not be used» is true.
I support THE PAYING CUSTOMERS ONLY.
1. An initial reusable source for a card with an optional 3D Secure support ("three_d_secure": "optional")
2. The derived single-use 3D Secure source