You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Description

Offer a simple checkout experience to your customers by allowing them to reuse their credit card data


Examples

Step 1 : Initial payment and Card registration

  • A customer makes a purchase of € 20.00 on the merchant's site.
  • He enters all the data necessary for payment (card number, expiration date, CVV, etc.).
  • The merchant offers his customer to register his card.

Step 2 : Offer a One-click payment

  • During his next purchase, the merchant offers the customer to reuse his card.
  • The customer can be authenticated (CIT - Customer initiated transaction)
  • The CVV is optionnal





Prerequisites

  • You offer your customers payment by credit card

  • Customers buy in your shop and you store the credit card data in the form of the pseudo card number

  • IMPORTANT: The following initial payment is subject to the liability shift for you as a merchant. In the case of the subsequent payment, however, this expires, so that there is no liability shift.



Implementation

Step 1 : Initial payment and Card registration

Axepta Online endpoint

The first payment can be done with :

  • Credit card form hosted by BNP Paribas  - PaySSL.aspx

  • Credit card form hosted by the merchant - PayNow.aspx - if PCI-DSS compliant


Authentication with 3D Secure is mandatory for the first transaction initiated by the customer (CIT) / card registration


Request

(info) The following table describes the additional encrypted payment request parameters that needs to be added to the request :


KeyFormatCNDDescriptionExample

credentialOnFile

JSONMObject specifying type and series of transactions using payment account credentials (e.g. account number or payment token) that is stored by a merchant to process future purchases for a customer. Required if applicable.


{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": true
}


threeDSPolicy

JSON

O

Object specifying authentication policies and excemption handling strategies.

Use : Mandate challenge

__


Response

Parameters that should be stored by the merchant and will be used for the next transactions


KeyFormatCNDDescription
cardJSONMCard response data


Step 2 : Offer a One-click payment

Axepta Online endpoint

The subsequent payment can be initiated by the merchant through PayNow.aspx.

The mechant doesn't need to be PCI-DSS because this feature requires the use of the PCNr (Pseudo Card Number not real PAN) which is stored by the merchant.


Authentication with 3D Secure is not mandatory for these transactions, so exemptions can be requested.

CVV is optionnal for One-click payments.



Request with paynow.aspx

Mechant creates a form with the following fields :

  • Number - Field hidden from user
  • securityCode - CVV entered by the buyer - Only "visible" field of the form
  • expiryDate - Field visible or hidden to the user
  • brand - Field visible or hidden to the user
  • cardholder - Field visible or hidden to the user


All details for integration are available here : Silent Order Post (PayNow.aspx)


(info) The following table describes the additional encrypted payment request parameters that needs to be added to the request :


KeyFormatCNDDescriptionExample
cardJSONMCard data--

credentialOnFile

JSONMObject specifying type and series of transactions using payment account credentials (e.g. account number or payment token) that is stored by a merchant to process future purchases for a customer. Required if applicable.


{
    "type": {
        "unscheduled": "CIT"
    },
    "initialPayment": false
}


browserInfoJSONMAccurate browser information are needed to deliver an optimized user experience. Required for 3DS 2.0 transactions.--

  • No labels