Processing data specific to the response of payment with

Characteristics of a split payment:

When paying, the buyer pays for a part of the purchase with a meal voucher and the remainder with a bank card.

The payment will consist of N sequences detailed in the vads_payment_seq field:

  • All the transactions of a split payment are combined within a payment sequence.
  • All the transactions of a payment sequence have the same transaction identifier, but a different sequence number.
  • The number of the first transaction of the sequence is 1, the number of the second is 2, etc.

The life cycle of a successful Titre-Restaurant transaction:

When the authorization request has been accepted, the status of the Titre-Restaurant transaction changes to "waiting for capture". This state is defined by the AUTHORISED value specified in the vads_trans_status field. The transaction is accepted and will be automatically transmitted to the issuer for refund on D+1.

Once the transaction has been transmitted to the issuer, its status changes to CAPTURED.

List of fields specific to the response of a meal voucher payment

The Instant Payment Notification URL will contain the following information:

Table 1. List of fields to analyze
Field name Description Value
vads_page_action Completed operation

PAYMENT

Payment made without token
vads_trans_status Status of the payment
  • AUTHORISED
    Accepted, waiting for capture until the payment is captured.
  • CAPTURED
    Captured when the payment is captured
  • REFUSED
    Transaction is declined
  • ABANDONNED
    Payment abandoned by the buyer
  • CANCELLED
    Payment canceled by the merchant
vads_card_brand Payment type Case of payment made using only a Titre-Restaurant card:
  • SODEXO, for a "Pass Restaurant" card
  • EDENRED for "Titre Restaurant Mastercard" card
  • CHQ_DEJ for "Chèque Déjeuner" card
  • APETIZ for "Apetiz" card

Case of a split payment (a Titre-Restaurant card is a complementary payment method):

  • MULTI
    The table of payment methods used by the buyer can be found in the JSON of the vads_payment_seq field (card_brand element).
vads_payment_seq Details of the split payment sequence See explanations and table below.

Details of the vads_payment_seq field

All the transactions of a split payment are combined within a payment sequence.

All the transactions of a payment sequence have the same transaction identifier, but a different sequence number. The number of the first transaction of the sequence is 1, the number of the second is 2, etc.

The vads_payment_seq field (json format) describes the split payment sequence. It contains:

  • "trans_id": identifier of the transaction received in the vads_trans_id field of the payment form.
  • "transaction": transaction table of the sequence.

Note: canceled and declined transactions are also displayed in the table.

Note: the field order in JSON is not necessarily the same as in your programming language.

Each transaction of the sequence contains the following elements:

Table 2. Contents of the JSON object
Name of the parameter Description
amount

Amount of the payment sequence.
operation_type

Debit operation.
auth_number

Authorization number. Example: 949478
auth_result Return code of the authorization request.
capture_delay Delay before the capture (in days).
  • For payments by meal vouchers (Titre-Restaurant), this parameter is set to"0".
  • For a payment by card, this parameter is the requested capture date (ISO 8601 format). If not sent in the payment form, the value defined in the Expert Back Office will be used.
card_brand

Used payment method.

For meal voucher payments, this parameter can be set to:
  • SODEXO, for a "Pass Restaurant" card
  • EDENRED for a "Ticket Restaurant" card
  • CHQ_DEJ for a "Chèque Déjeuner" card
  • APETIZ for a "Apetiz" card

See the Payment Gateway Implementation Guide available in our online documentation archive to see the complete list of card types.
card_number Payment method number
expiry_month

Expiry month of the payment method.

expiry_year

Expiry month year of the payment method.

payment_certificate Payment certificate.
contract_used Contract used for the payment.
identifier Unique identifier (token) associated with a payment method.
identifier_status Present only if the requested action corresponds to token creation or update.
Possible values:
Value Description
CREATED

The authorization request has been accepted.

Token (or UMR for SEPA payment) has been successfully created.
NOT_CREATED

The authorization request has been declined.

The token (or UMR for SEPA payment) has not been created, and therefore cannot be viewed in the Expert Back Office.
UPDATED Token (or UMR for SEPA payment) has been successfully updated.
NOT_UPDATED The token (or UMR for SEPA payment) has not been updated.
ABANDONED

The action has been abandoned by the buyer (debtor).

The token (or UMR for SEPA payment) has not been created, and therefore cannot be viewed in the Expert Back Office.
presentation_date

For a payments by card, this parameter is the requested capture date (ISO 8601 format).

For a payment by meal voucher processed by the Conecs scheme, this parameter value corresponds to the date of the order.
trans_id Transaction number.
ext_trans_id Parameter absent for bank card and meal voucher payments.
trans_uuid Unique reference generated by the payment gateway after a payment transaction has been created.

Provides a guarantee that each transaction is unique.
extra_result Numerical code of risk assessment result.
Code Description
Empty No verification made.
00 All the verification processes have been successfully completed.
02 The card has exceeded the authorized number of outstanding payments.
03 The card is on the merchant's greylist.
04 The card's country of origin is on the merchant's greylist.
05 The IP address is on the merchant's greylist.
06 The bin code is on the merchant's greylist.
07 E-carte bleue detection.
08 National commercial card detection.
09 Foreign commercial card detection.
14 Detection of a card with systematic authorization.
20 Coherence control: no corresponding countries (IP country, card country, buyer country).
30 The country of the IP address is on the greylist.
99 Technical issue encountered by the server during one of the local verification processes.
sequence_number Sequence number.
trans_status Transaction status.
Example of JSON format for a transaction made using accepted Titre-Restaurant and CB cards:
vads_payment_seq :{
	"trans_id":"011028",
	"transactions":[
		{
		"amount":"1000",
		"operation_type":"DEBIT",
		"auth_number":"3feee9",
		"auth_result":"10",
		"capture_delay":"0",
		"card_brand":"APETIZ",
		"card_number":"507596XXXXXX0028",
		"expiry_month":"6",
		"expiry_year":"2019",
		"payment_certificate":"90c0a80da281a5880675232bc007d19c799bdd01",
		"contract_used":"1999011",		
		"presentation_date":"2018-03-22T11:35:10Z",
		"trans_id":"012224",
		"trans_uuid":"b2a059f4b0164252844ccef94dcd3aa2",
		"sequence_number":"1",
		"trans_status":"AUTHORISED"
		},
		{
		"amount":"3504",
		"operation_type":"DEBIT",
		"auth_number":"3fb881",
		"auth_result":"00",
		"capture_delay":"0",
		"card_brand":"CB",
		"card_number":"497010XXXXXX0014",
		"expiry_month":"6",
		"expiry_year":"2019",
		"payment_certificate":"1395fe45833753c8f206f613a4fa237e41fea7a8",
		"contract_used":"5785350",		
		"presentation_date":"2018-03-22T11:35:14Z",
		"trans_id":"012224",
		"trans_uuid":"294897a937da4d7db48a222b727bb1e5",
		"sequence_number":"2",
		"trans_status":"AUTHORISED"
		}]
}

Example of JSON format for a transaction made using a Titre-Restaurant card that was rejected, canceled and then accepted followed by an accepted CB: 
vads_payment_seq :{
	"trans_id":"011029",
	"transactions":[
		{
		"amount":"1000",
		"operation_type":"DEBIT",
		"auth_number":"3fe235",
		"auth_result":"57"
		"capture_delay":"0",
		"card_brand":"SODEXO",
		"card_number":"507597XXXXXX0020",
		"expiry_month":"12",
		"expiry_year":"2020",
		"payment_certificate":"74db5c03b6cba5c763e520648b0071768f5d806f",
		"contract_used":"1999011",
		"presentation_date":"2018-01-29T14:34:20Z",
		"trans_id":"011028",
		"trans_uuid":"3670c65bb8e040d2996474b809e0c1ac",
		"sequence_number":"1",
		"trans_status":"REFUSED"		
		},
		{
		"amount":"1000",
		"operation_type":"DEBIT",
		"auth_number":"3fe235",
		"auth_result":"10"
		"capture_delay":"0",
		"card_brand":"SODEXO",
		"card_number":"507597XXXXXX0747",
		"expiry_month":"11",
		"expiry_year":"2020",
		"payment_certificate":"d396a0a9601dc88d23bba2224a41fe8c32676e2f",
		"contract_used":"1999011",
		"presentation_date":"2018-01-29T14:34:20Z",
		"trans_id":"011028",
		"trans_uuid":"5f5edf3fe22f4dbfbd53152417275b4c",
		"sequence_number":"2",
		"trans_status":"CANCELLED"	
		},
		{
		"amount":"1000",
		"operation_type":"DEBIT",
		"auth_number":"3fe235",
		"auth_result":"10"
		"capture_delay":"0",
		"card_brand":"APETIZ",
		"card_number":"507596XXXXXX0421",
		"expiry_month":"10",
		"expiry_year":"2020",
		"payment_certificate":"010a2db1ef864d6584424c41512dd9ad678c785e",
		"contract_used":"1999011",
		"presentation_date":"2018-01-29T14:34:20Z",
		"trans_id":"011028",
		"trans_uuid":"2cfee86ecf5e433ab0db82dc7b601db6",
		"sequence_number":"3",
		"trans_status":"AUTHORISED"		
		},
		{
		"amount":"3222",
		"operation_type":"DEBIT",
		"auth_number":"3fc022",
		"auth_result":"00"
		"capture_delay":"0",
		"card_brand":"CB",
		"card_number":"497010XXXXXX0014",
		"expiry_month":"6",
		"expiry_year":"2019",
		"payment_certificate":"d0739983a70cd0267f1b50f6377bada4f1d6857e",
		"contract_used":"5785350",
		"presentation_date":"2018-01-29T14:34:35Z",
		"trans_id":"011028",
		"trans_uuid":"60f3c247d0a842498cfc38421d60b391",
		"sequence_number":"4",
		"trans_status":"AUTHORISED"		
		}]		
}

Example of JSON format for a transaction made using accepted Titre-Restaurant and CB cards with registration of both cards:

vads_payment_seq :{
	"trans_id":"012224",
	"transactions":[
		{
		"amount":"1000",
		"operation_type":"DEBIT",
		"auth_number":"3fd375",
		"auth_result":"10",
		"capture_delay":"0",
		"card_brand":"APETIZ",
		"card_number":"507596XXXXXX0028",
		"expiry_month":"6",
		"expiry_year":"2019",
		"payment_certificate":"90c0a80da281a5880675232bc007d19c799bdd01",
		"contract_used":"1999011",
		"identifier":"0b621d0da984414b86193502cfd010ca",
		"identifier_status":"CREATED",
		"presentation_date":"2018-04-19T07:05:03Z",
		"trans_id":"257349",
		"trans_uuid":"d97a7a374e5e41359f3c97649f5777ae",
		"sequence_number":"1",
		"trans_status":"AUTHORISED"
		},
		{
		"amount":"3504",
		"operation_type":"DEBIT",
		"auth_number":"3fd375",
		"auth_result":"00",
		"capture_delay":"0",
		"card_brand":"CB",
		"card_number":"497010XXXXXX0014",
		"expiry_month":"6",
		"expiry_year":"2019",
		"payment_certificate":"db4cff0dce146571d7b2720f2b716a0d7c72b8f4",
		"contract_used":"5785350",
		"identifier":"432870832da94e73b39a6999475d4d27",
		"identifier_status":"CREATED",
		"presentation_date":"2018-04-19T07:05:45Z",
		"trans_id":"257349",
		"trans_uuid":"775769b823ad4cf3a16a41cb4f3401d5",
		"sequence_number":"2",
		"trans_status":"AUTHORISED"
		}]
}
Example of response for a successful single payment made using a Titre-Restaurant card without a JSON table
[...]
vads_page_action :PAYMENT
vads_currency :978
vads_payment_src :EC
vads_cust_email :example@example.com
vads_card_brand:SODEXO
vads_order_id :861-0097
vads_capture_delay :0
vads_auth_number :
vads_currency :978
vads_payment_config :SINGLE
vads_language :fr
vads_risk_control :CARD_FRAUD=OK
vads_operation_type :DEBIT
vads_card_number :507597XXXXXX0033
vads_result :00
vads_trans_uuid :fd7c645cf082466cb635699b70ba690f
vads_trans_date :20180129143412
vads_ctx_mode :TEST
vads_action_mode :INTERACTIVE
vads_amount :1900
vads_version :V2
vads_presentation_date :20180129143435
vads_trans_status :AUTHORISED
vads_pays_ip :FR
vads_trans_id :011028
vads_auth_result :00
vads_site_id :12345678
[...]
signature :d67320df4aaaae5ef1e8381785cddb116d7c6aa3