...
| Tip |
|---|
The minimum amount for CV Connect transactions is 20 euros. More details : CGV | Agence Nationale pour les Chèques Vacances (ancv.com) |
About ANCV Connect
General information about ANCV Connect
Cheque-Vacances Connect (cvconnect by ANCV) is a French initiative for travel vouchers. The customer pays for travel (related) expenses with travel vouchers at accredited merchants.
...
Further information can be found on the webpage of ANCV (https://www.ancv.com/).
Process flow chart
The payment platform interface
Definitions
Data formats:
a | alphabetical |
as | alphabetical with special characters |
n | numeric |
an | alphanumeric |
ans | alphanumeric with special characters |
ns | numeric with special characters |
bool | boolean expression (true or false) |
3 | fixed length with 3 digits/characters |
..3 | variable length with maximum 3 digits/characters |
enum | enumeration of allowed values |
dttm | ISODateTime (YYYY-MM-DDThh:mm:ss) |
...
Notice: Please note that the names of parameters can be returned in upper or lower case.
Call of the payment platform interface for ANCV Connect
To make a payment with ANCV Connect via Limonetik over the payment platform, go to the following URL:
Notice: For security reasons, the payment platform rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
...
MID | ans..30 | M | MerchantID, assigned by BNP Paribas |
PayID | an32 | M | ID assigned by the payment platform for the payment, e.g. for referencing in batch files. |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by the payment platform |
TransID | ans..64 | M | Merchant’s transaction number |
RefNr | ns..30 | O | Unique reference number |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
Status | a..50 | M | OK or FAILED |
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! |
Code | n8 | M | Error code according to the payment platform Response Codes (Error codes) |
CodeExt | ans..256 | C | Error code from Limonetik. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with BNP Paribas support. |
ErrorText | ans..256 | C | Detailed Limonetik error message. Notice: Is returned only if Status=FAILED. Use is possible only in agreement with BNP Paribas support. |
UserData | ans..1024 | O | If specified at request, the payment platform forwards the parameter with the payment result to the shop |
TransactionID | ans..50 | O | ID for identification of payment form |
Capture
Captures are possible via a Server-to-Server connection. To carry out a Capture for ANCV Connect via Limonetik via a Server-to-Server connection please use the following URL:
Notice: For security reasons, the payment platform rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
...
MerchantID | ans..30 | M | MerchantID, assigned by BNP Paribas. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by the payment platform for the payment to be captured |
TransID | ans..64 | M | TransactionID which should be unique for each payment |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a..3 | M | Currency code, three digits DIN / ISO 4217 |
RefNr | ns..30 | O | Merchant’s unique reference number |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
| ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, the payment platform will not carry out the payment, but will just return the status of the original transaction. Please note that the payment platform must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
The following table describes the payment platform response parameters:
MID | ans..30 | M | MerchantID, assigned by BNP Paribas |
PayID | an32 | M | ID assigned by the payment platform for the payment, e.g. for referencing in batch files. |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by the payment platform |
TransID | ans..64 | M | Merchant’s transaction number |
Status | a..50 | M | OK or FAILED |
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! |
Code | n8 | M | Error code according to the payment platform Response Codes (Error codes) |
RefNr | ns..30 | M | Merchant’s unique reference number |
Credit with reference
Credits (refunds) are possible via a Server-to-Server connection. For a Credit with reference to a capture the amount of the Credit is limited to the amount of the previous capture. To carry out a credit with a reference transaction, please use the following URL:
Notice: For security reasons, the payment platform rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
...
MerchantID | ans..30 | M | MerchantID, assigned by BNP Paribas. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by the payment platform for the payment to be credited |
TransID | ans..64 | M | TransactionID which should be unique for each payment |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a..3 | M | Currency code, three digits DIN / ISO 4217 |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
| ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, the payment platform will not carry out the payment, but will just return the status of the original transaction. Please note that the payment platform must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
The following table describes the payment platform response parameters:
MID | ans..30 | M | MerchantID, assigned by BNP Paribas |
PayID | an32 | M | ID assigned by the payment platform for the payment, e.g. for referencing in batch files. |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by the payment platform |
TransID | ans..64 | M | Merchant’s transaction number |
Status | a..50 | M | OK or FAILED |
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! |
Code | n8 | M | Error code according to the payment platform Response Codes (Error codes) |
Reversal
To cancel a transaction with ANCV Connect via Limonetik, please use the following URL:
Notice: For security reasons, the payment platform rejects all payment requests with formatting errors. Therefore please use the correct data type for each parameter.
...
MerchantID | ans..30 | M | MerchantID, assigned by BNP Paribas. Additionally this parameter has to be passed in plain language too. |
PayID | an32 | M | ID assigned by the payment platform for the payment to be reverted |
TransID | ans..64 | M | TransactionID which should be unique for each payment |
Amount | n..10 | M | Amount in the smallest currency unit (e.g. EUR Cent) Please contact the helpdesk, if you want to capture amounts < 100 (smallest currency unit). |
Currency | a..3 | M | Currency code, three digits DIN / ISO 4217 |
MAC | an64 | M | Hash Message Authentication Code (HMAC) with SHA-256 algorithm |
| ReqID | ans..32 | O | To avoid double payments, enter an alphanumeric value which identifies your transaction and may be assigned only once. If the transaction is submitted again with the same ReqID, the payment platform will not carry out the payment, but will just return the status of the original transaction. Please note that the payment platform must have a finalized transaction status for the first initial action. Submissions with identical ReqID for an open status will be processed regularly. |
The following table describes the payment platform response parameters:
MID | ans..30 | M | MerchantID, assigned by BNP Paribas |
PayID | an32 | M | ID assigned by the payment platform for the payment, e.g. for referencing in batch files. |
XID | an32 | M | ID for all single transactions (authorisation, capture, credit note) for one payment assigned by the payment platform |
TransID | ans..64 | M | Merchant’s transaction number |
Status | a..50 | M | OK or FAILED |
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! |
Code | n8 | M | Error code according to the payment platform Response Codes (Error codes) |
Batch processing via the interface
Basic information about using Batch files and about their structure you can find inside the separate manual for the Batch manager. Within batch processing not alle functions are available which are usually available for the online interface.
...
Capture | 1.0 / 2.0 | Standard version without return of parameter Code |
| 1.x / 2.x | with RefNr (valid for all versions other than 1.0) |
Credit | 1.0 / 2.0 | Standard version without return of parameter Code |
| 1.x / 2.x | with RefNr (valid for all versions other than 1.0) |
Reverse | 1.0 / 2.0 | Standard version without return of parameter Code |
| 1.x / 2x. | with RefNr (valid for all versions other than 1.0) |
The structure for a Limonetik payment within a Batch file to be submitted is the following:
HEAD,<MerchantID>,<Date>,<Version> Limonetik,Capture,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> Limonetik,Credit,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> Limonetik,Reverse,<Amount>,<Currency>,<TransID>,(<RefNr>,)<PayID> FOOT,<CountRecords>,<SumAmount> |
Example for Master MID Funktion:
| HEAD,[Master]MerchantID,Date,2.x Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action) FOOT,CountRecords,SumAmount |
The following table describes the individual fields and values used within the data set (record) in the batch file:
...
Action | a..20 | M | The parameter Action defines the type of transaction: Capture Credit Reverse (cancellation) |
PayID | an32 | M | ID for this transaction given by the payment platform |
Status | a..50 | M | OK or FAILED |
Code | n8 | M | Error code according to the payment platform Response Codes (Error codes) |