Add 3DS tokens to transaction error and billing info #415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This allows the client to use the new 3DSecure features of the API. This involves a 2 step flow with RecurlyJS, see recurly/recurly-js#527 for technical details on that side of this process.
Script 1: Attempt to update a billing info with a credit card that requires 3DS authentication:
The
ValidationError
'sTransactionError
(the first element of theerrors
array) will contain athree_d_secure_action_token_id
, which needs to be passed to RJS for authentication. Upon successful authentication, RJS will return a result token, which can then be passed with the billing info.Script 2: Update the billing info using 3DS:
This flow still applies when passing a
billing_info
object to the/accounts
,/subscriptions
, and/purchases
endpoints.