Difference between revisions of "Token payment upgrade to 3DS"

From Barion Documentation
Jump to navigation Jump to search
Line 1: Line 1:
 
{{PageTitle|title=Upgrading token payment implementation to use 3DS}}
 
{{PageTitle|title=Upgrading token payment implementation to use 3DS}}
 +
 +
 +
[[Token_payment|Token payment]] is a solution that enables the merchant to charge the customer without requiring the presence of the customer. It is a powerful tool to conduct subscription-like or customer not present scenarios. This scenario required the merchant to create a token that would act as an identifier for the customer's funding source (may it be a credit card or a Barion e-money account). To acquire such a token the merchant had to do several things:
 +
# Create an alphanumeric token
 +
# Register this token in the Barion system by attaching it to an initial payment and having the customer fulfill that payment (either by card or form an e-money account)
 +
# Refer to this token in a subsequent payment attempt
 +
 +
This meant that as far as this token referred to a valid and still available funding source the merchant could create payments without any limitations.
  
 
{{NotificationBox|title=IMPORTANT|text=Starting from January 1 the [[3DSecure|3DS authentication]] will be mandatory for all of our partners!|color=#FF7A3D}}
 
{{NotificationBox|title=IMPORTANT|text=Starting from January 1 the [[3DSecure|3DS authentication]] will be mandatory for all of our partners!|color=#FF7A3D}}

Revision as of 17:00, 16 November 2020

Upgrading token payment implementation to use 3DS


Token payment is a solution that enables the merchant to charge the customer without requiring the presence of the customer. It is a powerful tool to conduct subscription-like or customer not present scenarios. This scenario required the merchant to create a token that would act as an identifier for the customer's funding source (may it be a credit card or a Barion e-money account). To acquire such a token the merchant had to do several things:

  1. Create an alphanumeric token
  2. Register this token in the Barion system by attaching it to an initial payment and having the customer fulfill that payment (either by card or form an e-money account)
  3. Refer to this token in a subsequent payment attempt

This meant that as far as this token referred to a valid and still available funding source the merchant could create payments without any limitations.

IMPORTANT
Starting from January 1 the 3DS authentication will be mandatory for all of our partners!