3DS FAQ: Difference between revisions

From Barion Documentation
Jump to navigation Jump to search
(23 intermediate revisions by the same user not shown)
Line 2: Line 2:


== Upon starting the payments which properties are required? ==
== Upon starting the payments which properties are required? ==
The new properties marked with 3DS badge are highly recommended. (Read: error won't be thrown, when sent without these properties). These content of these fields are optional. Payments undergo Transaction Risk Analysis on the card issuer side based on these data as well, deciding if the payment should be challenged or not.
<div>The new properties marked with {{3dsfield}} badge in the [[Payment-Start-v2|PaymentStart]] request are highly recommended. (Read: error won't be thrown, when sent without these properties). These content of these fields are optional. Payments undergo Transaction Risk Analysis on the card issuer side based on these data as well, deciding if the payment should be challenged or not.</div>


== Are TraceId required for earlier initialized token payments after 2021.02.01? ==
== Are TraceId required for earlier initialized token payments after 2021.02.01? ==
First yes, TraceIds are not required for earlier initialized token payments without 3DS for an INTERIM period. After this period expires (potentially 2021 Q3) TraceIds will be required for all Token Payments.
TraceIds are not required for OneClick payments. For an interim perdio (until 2021.02.01) TraceIds will be required for all MerhcantInitiatedPayments and RecurringPayments.


== We've received TraceId in the following format: <code>0MHSGZRZ1G0118      0</code>==
== We've received TraceId in the following format: <code>0MHSGZRZ1G0118      0</code>==
The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact.
The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact. You can read more about the TraceId [[Token_payment_3D_Secure#TraceId|here]]


== Can we skip the additional data in subsequent payments required for 3DS authentication in the first Token Payment? ==
== Can we skip the additional data in subsequent payments that were required for 3DS authentication in the first Token Payment? ==
Wrong! The difference between the initial and subsequent token payment is that 3DS authentication is only required for the first, initial payment. More info can be found [[Token_payment_3D_Secure|here]]
Additional data can't be ignored! The difference between the initial and subsequent token payment is that 3DS authentication is only required for the first, initial payment. More info can be found [[Token_payment_3D_Secure|here]]


== Do we have to generate the "TraceId" in the first Payment/Start, or is it generated by Barion? ==
== Do we have to generate the TraceId in the first [[Payment-Start-v2|Payment/Start]], or is it generated by Barion? ==
TraceId is generated by the Card Issuer, so it is not required in the initial Payment6Start. You have to store the TraceId, recived int ghe GetPaymentState, and send in all subsequent payments. You can read more [[Token_payment_3D_Secure#1.3_Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|here]]. The exceptions are the subsequent payments of an already initialized token payments without 3DS. More info can be found [[Token_payment_3D_Secure#Changing_the_token_payment_scenario_with_an_existing_token|here]]
TraceId is generated by the Card Issuer, so it is not required in the initial [[Payment-Start-v2|Payment/Start]] request. You have to store the TraceId, received in the [[Payment-GetPaymentState-v2|GetPaymentState]] response, and send it in all subsequent payments. You can read more [[Token_payment_3D_Secure#1.3_Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|here]]. The exceptions are the subsequent payments of an already initialized token payments without 3DS. More info can be found [[Token_payment_3D_Secure#Changing_the_token_payment_scenario_with_an_existing_token|here]]


== When the amount of the first payment is different than the rest, I have to use MechantInitiatedPayment and not Recurring. Right? ==
== When the amount of the first payment is different than the rest, I have to use [[RecurrenceType|MechantInitiatedPayment]] and not [[RecurrenceType|RecurringPayment]]. Right? ==
Yes, RecurringPayment can only be used, when the amounts of all the subsequent payments are the same. If only 1 is different (eg. you give discount/free for the first month), only MechantInitiatedPayment can be used.
Yes, RecurringPayment can only be used, when the amounts of all the subsequent payments are the same or less. If only 1 is different (eg. you give discount/free for the first month), only MechantInitiatedPayment can be used. You can find more info [[Token_payment_3D_Secure#Token_payment_scenarios|here]].

Revision as of 09:49, 22 January 2021

Upon starting the payments which properties are required?

The new properties marked with
3DS
badge in the PaymentStart request are highly recommended. (Read: error won't be thrown, when sent without these properties). These content of these fields are optional. Payments undergo Transaction Risk Analysis on the card issuer side based on these data as well, deciding if the payment should be challenged or not.

Are TraceId required for earlier initialized token payments after 2021.02.01?

TraceIds are not required for OneClick payments. For an interim perdio (until 2021.02.01) TraceIds will be required for all MerhcantInitiatedPayments and RecurringPayments.

We've received TraceId in the following format: 0MHSGZRZ1G0118 0

The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact. You can read more about the TraceId here

Can we skip the additional data in subsequent payments that were required for 3DS authentication in the first Token Payment?

Additional data can't be ignored! The difference between the initial and subsequent token payment is that 3DS authentication is only required for the first, initial payment. More info can be found here

Do we have to generate the TraceId in the first Payment/Start, or is it generated by Barion?

TraceId is generated by the Card Issuer, so it is not required in the initial Payment/Start request. You have to store the TraceId, received in the GetPaymentState response, and send it in all subsequent payments. You can read more here. The exceptions are the subsequent payments of an already initialized token payments without 3DS. More info can be found here

When the amount of the first payment is different than the rest, I have to use MechantInitiatedPayment and not RecurringPayment. Right?

Yes, RecurringPayment can only be used, when the amounts of all the subsequent payments are the same or less. If only 1 is different (eg. you give discount/free for the first month), only MechantInitiatedPayment can be used. You can find more info here.