You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If setBillingAgreementDetails returns a constraint, handle them as described in Step 2: Set purchase details and define the purchase of the Amazon Pay and Login with Amazon integration guide. Otherwise, proceed and call the confirmBillingAgreement operation.
The confirmBillingAgreement operation requires the following input parameters...
and in the example there is a call to client.confirm_order_reference (which is not mentioned in the integration steps for AUTOMATIC PAYMENTS):
Is client.confirm_order_reference used for automatic payments too?
If yes then is amazon_order_reference_id the same as BillingAgreement Id?
If not what are the correct steps to be SCA compliant for automatic payments with merchant initiated transactions?
The text was updated successfully, but these errors were encountered:
We are working on the necessary changes to the Ruby SDK now. We will publish it once we complete testing. There will be new attributes added in the confirm_billing_agreement and set_billing_agreement_details calls.
The upcoming PSD2 forces SCA for all our future payments.
Based on the docs (https://developer.amazon.com/docs/eu/amazon-pay-automatic/sca-upgrade-merchant-initiated-transactions.html#change-the-process-to-set-up-a-new-billing-agreement),
it states:
Is client.confirm_order_reference used for automatic payments too?
If yes then is amazon_order_reference_id the same as BillingAgreement Id?
If not what are the correct steps to be SCA compliant for automatic payments with merchant initiated transactions?
The text was updated successfully, but these errors were encountered: