Difference between revisions of "3DS FAQ"

From Barion Documentation
Jump to navigation Jump to search
 
(28 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!
+
<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>
  
== 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 2021.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.
+
TraceIds are not required for OneClick payments. For an interim perdio (until 2021.02.01) TraceIds will be required for all MerhcantInitiatedPayments and RecurringPayments.
  
== 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. You can read more about the TraceId [[Token_payment_3D_Secure#TraceId|here]]
  
== 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 that were 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#1.3_Processing_the_callback_and_requesting_information_about_the_result_of_the_payment|itt]] van info.
+
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]]
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:
 
  
== A leírás alapján, ha az első havi díj különbözik a többitől, akkor a MechantInitiatedPayment-et kell alkalmaznom és nem a Recurring-et. Igaz? ==
+
== Do we have to generate the TraceId in the first [[Payment-Start-v2|Payment/Start]], or is it generated by Barion? ==
Igen, RecurringPayment csak akkor indítható, ha az összes subsequent fizetés összege megyezik. Ha az összeg akár csak 1 esetben is különbözik (pl első havi csökkentettt/ingyenes havidíj), csak MerchantInitiatedPayment-ként indítható.
+
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]]
  
== A korábban létrehozott token alapú recurring payment esetén nem fog kellene traceid 02.01-től sem? Azaz azokat nem kell megváltoztatni csak az új fizetéseket?==
+
== When the amount of the first payment is different than the rest, I have to use [[RecurrenceType|MechantInitiatedPayment]] and not [[RecurrenceType|RecurringPayment]]. Right? ==
Egyrészt igen, egy ÁTMENETI ideig nem fog kelleni február 1-e után sem a TraceId a 3DS nélkül indított tokenekre, viszont ennek letelte után (várhatóan 2021 Q3) minden recurrenceId-hoz szükség lesz a TraceId-ra.
+
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]].

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