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

Compare with Current View Page History

« Previous Version 2 Next »

Scenario Cartes Bancaires Account Updater

(warning)(warning)(warning) DRAFT (warning)(warning)(warning)

Not implemented yet. 

No CB certificate yet


Cartes Bancaires Account Updater (short MDC) is a service provided by Cartes Bancaires (CB) which allows to request some credit card data, CB will check forupdates and sends updated credit card data back in response. 

To ease usage of MDC and to make it PCI DSS compliant Computop Paygate will translate Pseudo Card Numbers (PCNr) into credit card numbers before sending to MDC and will create new PCNr for updated cards before sending response back to you.

MDC / Computop Paygate allow you to send multiple cards in request will send a record back in response for each card you've sent.

(info)  Your Merchant confirguration needs to be enrolled to the Cartes Bancaires Account Updater (short MDC) by Computop Helpdesk

(info)  Only cards should be sent which are going to expire within 3 (?) months - not all cards.

(info)  You may send in real card numbers (pay attention to your PCI DSS certification) or Pseudo Card Numbers (PCNr) which are not PCI DSS relevant.

(info) Maximum number of cards in request / response is limited to 10.000 cards.


Request / Response mdcupdater.aspx

Request Elements

Notice: For security reasons, Computop Paygate rejects all payment requests with formatting errors. Therefore, please use the correct data type for each parameter.

The following table describes the encrypted payment request parameters:


Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

KeyFormatCNDDescription

MerchantID

ans..30

M

MerchantID, assigned by Computop. Additionally this parameter has to be passed in plain language too.

KeyFormatCNDDescription
TransID

ans..64

MTransactionID provided by you which should be unique for each payment

KeyFormatCNDDescriptionBeschreibung
cardsJSONM

List of cards to be checked, base64 encoded

Cards may be real PANs or PCNr, List of incoming cards may have up to 10.000 elements

incoming JSON like

[
    { "oldPan": "0123456789012907" },
    { "oldPan": "0123456789012000" }
]
e.g. cards=Ww0KICAgIHsgIm9sZFBhbiI6ICIwMTIzNDU2Nzg5MDEyOTA3IiB9LA0KICAgIHsgIm9sZFBhbiI6ICIwMTIzNDU2Nzg5MDEyMDAwIiB9DQpd


Typean4M

Fixed value = CB2A



Response Elements (mdcupdater.aspx)

The following table describes the result parameters with which the Computop Paygate responds to your system

(info) pls. be prepared to receive additional parameters at any time and do not check the order of parameters

(info) the key (e.g. mid, RefNr) should not be checked case-sentive

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

KeyFormatCNDDescription

mid

ans..30

M

MerchantID, assigned by Computop

 

KeyFormatCNDDescription
TransID

ans..64

MTransactionID provided by you which should be unique for each payment

KeyFormatCNDDescriptionBeschreibung

Status

a..20

M

Status of the transaction.

Values accepted:

  • OK

  • FAILED

Status der Transaktion.

Zulässige Werte:

  • OK
  • FAILED

KeyFormatCNDDescription
Description

ans..1024

M
Further details in the event that payment is rejected. Please do not use the Description but the Code parameter for the transaction status analysis!

KeyFormatCNDDescription
Code

an8

M

Error code according to Paygate Response Codes (A4 Error codes)

 

KeyFormatCNDDescriptionBeschreibung
cardsJSONM

List of cards, base64 encoded

newPan will always be a PCNr.

If newPan != oldPan then create new PCNr

response JSON like:

[
  { "oldPan": "12345678907", "newPan": "12345678917", "newExpiryDate": "10/23", "responseCode": "000" },
  { "oldPan": "2017671234560000", "newPan": "", "newExpiryDate":"", "responseCode": "301" }
]
e.g. cards=
Ww0KICB7ICJvbGRQYW4iOiAiMTIzNDU2Nzg5MDciLCAibmV3UGFuIjogIjEyMzQ1Njc4OTE3IiwgIm5ld0V4cGlyeURhdGUiOiAiMTAvMjMiLCAicmVzcG9uc2VDb2RlIjogIjAwMCIgfSwNCiAgeyAib2xkUGFuIjogIjIwMTc2NzEyMzQ1NjAwMDAiLCAibmV3UGFuIjogIiIsICJuZXdFeHBpcnlEYXRlIjoiIiwgInJlc3BvbnNlQ29kZSI6ICIzMDEiIH0NCl0=


Table of responseCodes:

responseCodesDescription

000

OK

Card has been found, new Card (newPan) has been returned. This card number is a PCNr due to ease PCI DSS compliance. 

201

Required element missing

Name of required element(s) that was omitted; if more than one element is detected, this is a comma delimited list.

203

Format Invalid (Data element not in the required format or value is invalid) For example, not numeric or wrong length.

301

There is no new card available for this pan

302

Data encryption/decryption failure (due to technical or other reason)

303

An error occured during the insert / update / delete within the database

304

Already existing in database

XXX

No PCNr found to be translated into PAN for MDC request


  • No labels