Difference between revisions of "3DS FAQ"

From Barion Documentation
Jump to navigation Jump to search
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
__TOC__
 
__TOC__
  
== Ilyen formátumú TraceID-ket kapunk tőletek: <code>0MHSGZRZ1G0118      0</code>==
+
== Upon starting the payments which properties are required? ==
Ezeket a kártyakibocsátó generálja. 100 karakteren belül bármi lehet, és a 0-k és szóközök fontosak, nem lehagyhatóak!
+
These 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.
  
== TokenPayment subsequent fizetéseknél már nem kell megadni a 3DS azonosításhoz szükséges adatokat? ==
+
== Are TraceId required for earlier initialized token payments after 02.01? ==
De! A RecurringPayment-ekhez leírás itt: [[Token_payment_3D_Secure|Token Payment 3DS]] Subsequent paymenteknél annyi változik, hogy az ügyfélhitelesítés nem történik meg.
+
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 Token Payments.
  
== A fizetések elindítása során megadott adatok közül mi az, ami kötelező megadni, hogy 3D Secure biztos legyen? ==
+
== We've received TraceId in the following format: <code>0MHSGZRZ1G0118      0</code>==
Ezek a mezők új 3ds fizetések esetén ERŐSEN JAVASOLTAK. (Értsd – az endpoint nem dob hibát, ha nélkülük érkezik a request.) A tartalmukban a fieldek opcionálisak (elvileg beküldhető üres array/map). Azonban a több = jobb elv érvényesül. A kártyakibocsátó ezeket a mezőket felhasználja a kockázati elemzés során és ennek megfelelően dönthet a tranzakció elutasításáról / challenge kéréséről / challenge nélküli jóváhagyásról.
+
The TraceId is generated by the card issuer, and can be anything up to 100 characters. Whitespaces and 0s should also be left intact.
  
== Az első Payment/Start kérésnél, a “TraceId” értékét nekünk kell legenerálni és megadni, vagy pedig ezt a Barion rendszere generálja le ?==  
+
== Can we skip the additional data in subsequent payments required for 3DS authentication in the first Token Payment? ==
A TraceId-t a kártyakibocsátó generálja, tehát az token inicializálásnál nem kell küldeni. Nektek tárolni kell a kapott TraceId-t és subsequent paymenteknél küldeni. Erről [[Token_payment_3D_Secure:Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|itt]] van info.
+
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]]
Ez alól kívételt képez egy ideig a már inicializált ismétlődő fizetések ismételt fizetései. Erről [[Token_payment_3D_Secure#Changing_the_token_payment_scenario_with_an_existing_token|itt]] van info:
+
 
 +
== 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 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]]
 +
 
 +
== When the amount of the first payment is different than the rest, I have to use MechantInitiatedPayment and not Recurring. 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.

Revision as of 17:56, 20 January 2021

Upon starting the payments which properties are required?

These 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.

Are TraceId required for earlier initialized token payments after 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 Token Payments.

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.

Can we skip the additional data in subsequent payments 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 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 Payment6Start. You have to store the TraceId, recived int ghe GetPaymentState, and send 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 Recurring. 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.