Introduction

WL Sips is a secure multi-channel e-commerce payment solution that complies with the PCI DSS standard. It allows you to accept and manage payment transactions by taking into account business rules related to your activity (payment on despatch, deferred payment, recurring payment, payment in instalments, etc.).

The purpose of this document is to explain the WL Sips Account Updater Service integration.

Who does this document target?

This document is intended to help you integrate the WL Sips Account Updater Service.

WL Sips Account Updater Service is based on the Account Updater services provided by the acquirers.

Before integrating the service, please verify with your customer support the service is available with your acquirer.

Contacting the support

For any technical question or request for assistance, our services are available:

  • by telephone at: +33 (0) 811 10 70 33
  • by e-mail: sips@worldline.com

In order to facilitate the processing of your requests, please provide your merchantId (15-digit number).

About WL Sips account updater service

For many years, you have used a recurring payment service to charge for your goods.

Typical examples include:

  • Insurance schemes
  • Breakdown and recovery services
  • Magazine and membership services.

Although this system has provided convenience for you and cardholders alike, there is one major drawback: plastic cards are regularly re-issued, and you can easily lose the track of the cardholders’ card details and the resulting chargebacks have proved to be unacceptable to all parties.

The purpose of the Account Updater Service, which was inaugurated by the issuers and acquirers, is to address this problem.

The AUS goals are to:

  • Provide you with an automated methods of updating your customers card details, enabling them to submit more accurate Recurring Payments for authorisation and settlement.
  • Help to minimise the risk of chargebacks.
  • Enable cardholders to request ''stop payments'' via their issuers.
  • Provide card issuers and acquirers with a more robust proposition for our future, prospective customers.

General principles

Account updater service general process :

Account Updater Service is based on the offline exchange of files.

  1. You send the enquiry files containing a list of cards to be verified by WL Sips via FTP. The request file has to be transferred in an archive file in ZIP format. The name of this archive file must be AUSREQxx.ZIP with xx which is a number between 01 and 99. One archive file must include only one request file. You have to use the following pattern for the filename:

    [ AUS ].[ Alias ].[ file_ID ]_REQ.[ Timestamp ] with:

    [AUS] Indicated that is a request file for “AUS batch”.
    [Alias] Merchant_ID is the WL Sips merchant ID.
    [file_ID] File_ID of enquiry file, a six digits number where the both first digits match with the XX value of archive file.
    [Timestamp] Date of the file in YYMMDD format & Time of the file in HHMMSS format.

  2. The request file is processed by WL Sips . Before transmitting the file to the acquirer, WL Sips verifies the validity and format of the file.
  3. Once all responses are sent back to WL Sips , WL Sips generates a response file containing a response for each of card in the enquiry file.
    1. If tokens and pans are sent by you, WL Sips sends updated tokens back to you in enquiry response file.
    2. If walletId/paymentMeanId, WL Sips updates cards in the wallet.

    A response code is associated to each card. For the response code, please refer to Response codes . If there is no response from the acquirer, a specific response code will be associated to the card.

  4. WL Sips sends this response file to the your FTP account.
  5. You download the response file from the FTP account provided by Worldline .
  6. The response file is transferred in an archive file in ZIP format. The name of this archive file is AUSREQxx.ZIP with xx matches with the value linked to the request file archive. One archive file includes only one request file. The merchant response file uses the following pattern for the filename:

    [ AUS ].[ Alias ].[ file_ID ]_REQ.[ Timestamp ] with:

    [AUS] Indicated that is a request file for “AUS batch”.
    [Alias] Merchant_ID is the WL Sips merchant ID.
    [file_ID] File_ID of enquiry file, a six digits number where the both first digits match with the XX value of archive file.
    [Timestamp] Date of the file in YYMMDD format & Time of the file in HHMMSS format.

  7. The response file is destroyed after the first successful download by you.

You need to take into account the updates for the subsequent payments.

There are 3 ways to identify a card in the enquiry file generated by you:

  • PAN
  • Token
  • Wallet ID/Payment mean ID

Beware that if you choose to use PAN or token to identify the card, the same card enrolled in the wallet is not updated.

For more details on the enquiry and response files, please refer to Your Enquiry Response File Specification .

You receive as many response files as the enquiry files you send. If you send a request file containing only VISA card, you should receive a response file after about 2 hours, otherwise you will receive response file after about 24 hours. The maximum delay is 25 hours.

Frequency

WL Sips service is available six days per week (Monday to Saturday), between 09.00 and 17.00. Within these parameters, customers can submit files whenever they wish, be it daily, weekly, or monthly.

Additionally, on any given day, you can submit one or more enquiry file(s) per day. WL Sips will send one response for each of enquiry files after maximum 25 hours ( WL Sips needs to wait for all responses for Visa cards after about 2 hours and for MasterCard after about 24 hours.).

Limitations

Reminder: Because there is a constraint from schemes, the maximum number of enquiry records permit per file is one hundred thousand records.

Your enquiry request/response file description

Your enquiry request file specification

Description

Header

Fields Format Presence Description
Tag name fixed at the ''header'' value ANS20 Mandatory Indicates a header registration.
merchantId N15 Mandatory Identifier of the shop, this value is provided to you by WL Sips during the shop registration.
date XML date Mandatory Date the file was created in your time zone (YYYY-MMDD+hhmm).
Time XML time Mandatory Time the file was created in the merchant's time zone (hh:mm:ss+hhmm).
merchantVolumeNumber AN6 Mandatory Permanently assigned by the Customer to uniquely identify this volume.
Complete Space or Zero filling not permitted.
The first 2 digits of volume number are assigned by Worldline . The 4 other digits are assigned by you. Please contact your customer contact for the number.
accountUpdateType ANS20 Mandatory The type of identifier of the account to be updated.
Values:
  • PAN
  • TOKEN
  • MERCHANTWALLET

Body

Fields Format Presence Description
Tag name fixed at the ''updateAccount'' value ANS20 Mandatory
recordSequence N6 Mandatory The attribute indicates the line number allowing you to reconcile the response with the request.
accountUpdateValue ANS35 Conditional The identifier of the account to be updated.
Mandatory: if accountUpdateType=PAN - tokenpan.
Mandatory: if accountUpdateType=TOKEN - token
Optional: if accountUpdateType= MERCHANTWALLET - masked pan
panExpiryDate N6 (YYYYMM) Conditional Expiry date of card.
Mandatory: if accountUpdateType=PAN/TOKEN
merchantWalletId ANS21 Conditional Customer's Wallet identifier.
Mandatory: if accountUpdateType=MERCHANTWALLET
paymentMeanId N6 Conditional Payment mean rank in the Buyer's wallet. Mandatory: if accountUpdateType=MERCHANTWALLET
amount N12 Optional Amount of the transaction in minor currency.
currencyCode "N3 (restricted values / ISO4217)" Optional Transaction Currency Code
merchantTransaction DateTime ANS25 (ISO8601) Optional Predicted date of financial transaction
transactionFrequency N1 Optional Transaction Frequency
0 – Ad Hoc
1 – Daily
2 – Weekly
3 – Every 2 weeks
4 – Monthly
5 – Quarterly
6 – Half Yearly
7 – Yearly
8 – Other (regular frequency)
merchantPolicyReference Number AN20 Mandatory Your contract/policy number for the agreement between you and the cardholder to which the Recurring Payment relates.

Footer

Fields Format Presence Description
Tag name fixed at the ''end'' value ANS20 Mandatory Indicates the end registration.
numberOfRecords N6 Mandatory Number of enquiry records in file Please refer to Processing response codes .

Your enquiry request file example

      <?xml version="1.0" encoding="UTF-8"?>
<file>
    <header>
        <merchantId>00000000000012</merchantId>
        <date>2016-10-25+02:00</date>
        <time>09:30:15+02:00</time>
        <merchantVolumeNumber>000005</merchantVolumeNumber>
        <accountUpdateType>PAN</accountUpdateType>
    </header>
    <body>
        <updateAccount recordSequence="1">
            <accountUpdateValue>5571000001001234</accountUpdateValue>
            <panExpiryDate>201805</panExpiryDate>
            <merchantPolicyReferenceNumber>01234567890123456789</merchantPolicyReferenceNumber>
        </updateAccount>
        <updateAccount recordSequence="2">
            <accountUpdateValue>5671000001004321</accountUpdateValue>
            <panExpiryDate>201610</panExpiryDate>
            <merchantPolicyReferenceNumber>98765432100123456789</merchantPolicyReferenceNumber>
        </updateAccount>
    </body>
    <end nbRecord="2"/>
</file>
    

Your enquiry response file specification

Description

Header

Fields Format Presence Description
Tag name fixed at the ''header'' value ANS20 Mandatory Indicates a header registration.
merchantId N15 Mandatory Identifier of the shop, this value is provided to you by WL Sips during the shop registration.
Date XML date Mandatory Date the file was created in your time zone (YYYY-MMDD+ hh:mm).
With CSV file format, timezone is YYYY-MM-DD+hhmm.
Time XML time Mandatory Time the file was created in your time zone (hh:mm:ss+hh:mm).
With CSV file format, timezone is hh:mm:ss+hhmm.
merchantVolumeNumber AN6 Mandatory Your volume number that you have sent in the request.
accountUpdateType ANS20 Mandatory The type of identifier of the account to be updated.
Values:
  • PAN
  • TOKEN
  • MERCHANTWALLET
processingResponse Code AN2 Mandatory Please refer to Processing response codes .

Body

Fields Format Presence Description
Tag name fixed at the ''updateAccount'' value ANS20 Mandatory
recordSequence N6 Mandatory The attribute indicates the line number allowing you to reconcile the response with the request.
accountUpdateValue ANS35 Conditional The identifier of the account to be updated.
Populated only if accountUpdateResponseCode =“01”

If accountUpdateType =PAN  tokenpan

If accountUpdateType =TOKEN  token.
If accountUpdateType = MERCHANTWALLET  masked pan.
panExpiryDate N6 (YYYYMM) Conditional Expiry date of card.
Populated only if accountUpdateResponseCode =“01” and accountUpdateType =PAN/TOKEN.
merchantWalletId ANS21 Conditional Customer's Wallet identifier.

Populated only if accountUpdaterResponseCode =“01” and if accountUpdateType =MERCHANTWALLET

paymentMeanId N6 Conditional Payment method rank in the customer's wallet.
Populated only if accountUpdateResponseCode =“01”.
Mandatory if accountUpdateType =MERCHANTWALLET.
accountUpdateResponseCode AN2 Mandatory Account updater service response code.
Please refer to Response codes .
acquirerNativeResponseCode ANS10 Optional Response code returned by the acquirer, in its own codification, during an account update service request.
Please refer to Response codes .
schemeResponseCode AN3 Optional Response code returned by the scheme.

Footer

Fields Format Presence Description
Tag name fixed at the ''end'' value ANS20 Mandatory Indicates the end registration
numberOfRecords N6 Mandatory Number of enquiry records in file.
The number should be:
  • the same with your request,
  • or zero, if the file is not handled by WL Sips .

Your enquiry response file example

      <?xml version="1.0" encoding="UTF-8"?>
<file>
    <header>
        <merchantId>00000000000012</merchantId>
        <date>2016-10-25+02:00</date>
        <time>09:30:15+02:00</time>
        <merchantVolumeNumber>000005</merchantVolumeNumber>
        <accountUpdateType>MERCHANTWALLET</accountUpdateType>
        <processingResponseCode>00</processingResponseCode>
    </header>
    <body>
        <updateAccount recordSequence="1">
            <merchantId>00000000000012</merchantId>
            <accountUpdateType>MERCHANTWALLET</accountUpdateType> 
            <accountUpdateValue>5571########1234</accountUpdateValue>
            <panExpiryDate>201805</panExpiryDate>
            <merchantWalletId>11112222333344441</merchantWalletId>
            <paymentMeanId>112345</paymentMeanId>
            <accountUpdateResponseCode>01</accountUpdateResponseCode>
            <acquirerNativeResponseCode>01</acquirerNativeResponseCode>
        </updateAccount>
    </body>
    <end nbRecord="1"/>
</file>
    

Processing response codes

Code Description
00 File processed correctly.
03 Invalid Merchant contract
06 The number of operations exceeds the maximum possible amount. The maximum number of operations is reached.
07 Number of records counted differently to the number indicated in the nbRecord field.
30 Format error
40 You don't register for account updater service.
90 The service is not available temporarily.
99 Temporary problem at the WL Sips server level.

Response codes

In the response, a response code is affected for each card in the enquiry file.

accountUpdateResponseCode Description Recommended action acquirerNativeResponseCode

VISA Response Mapping

acquirerNativeResponseCode

M/Card Response Mapping

acquirerNativeResponseCode

M/Card Error Response Mapping

00 No change Charge cardholder using existing. 01- No Change V – No change
04 No change Retry in 7 days. 03 – PAN currently being switched to new bank. Retry in 7 days.
01 Update provided Validate update data and charge cardholder using new details. 00 – New details found 04 – New expiry date found in VAU.
05 – Older expiry date found in VAU.
A- UPDATE. Match made, update data provided, includes replacement account, brand flip and portfolio flip.
E – EXPIRY. Match made, expiration date changed.
06 Update provided If AUS updated data is poor quality, contact cardholder for update. 06 – A more recent PAN has been found but it is already expired.
07 – A newer expiry date has been found but it is already expired.
02 Authority withdrawn or suspended Contact cardholder – do not charge. 51 – RP should be Stopped at PAN level.
52 – RP should be Stopped at merchant level 53 – RP should be Stopped at MPRN-level.
000200 – A Stop payment has been requested for this merchant by the cardholder.
No updates can be provided. Contact cardholder.
05 Not available Charge cardholder using existing details. 18 – Issuer not subscribed.
19 – PAN not found in VAU.
21 – BIN not participating in VAU.
27 – Cardholder has opted-out of VAU.
U - Unknown
03 Account closed Contact cardholder – do not charge. 02 – PAN has been switched to a non-Visa issuing bank.
20 – Closed account or temporarily unavailable for transactions.
C – CONTACT. Match made, account closed.
12 Submission error Verify data is correct and resubmit. Contact cardholder if appropriate. 12 – Field PAN invalid.
14 – Field AMOUNT invalid.
16 – Field FREQUENCY invalid.
17 – Field DATE invalid.
23 – MPRN invalid.
23 – MPRN invalid.
26 – Expiry date invalid format.
Spaces – if request has an error. 000101 – Error on submission – Non-numeric account number.
000102 – Error on submission – Bad check digit on account.
000103 – Error on submission – Invalid card expiry date.
000104 – Error on submission.
– Merchant not registered.
A0 Response not received from acquirer Resubmit