How to test
Find out how to test your implementation
Simple simulation using the simulator
Authorisation
{
"cardId": "cardId",
"cardAuthorizationDetail": {
"amount": {
"value": "2.00",
"currency": "EUR"
},
"localAmount": {
"value": "2.00",
"currency": "EUR"
},
"convertionRate": 1,
"merchantId": "123456789876543",
"merchantSiret": "123456789876543",
"merchantName": "123456789876543",
"merchantAddress": {
"street": "1 rue Louis Dupont",
"city": "Paris",
"zipCode": "75000",
"country": "FR"
},
"merchantAcquirerId": "123456789876543",
"merchantCategoryCode": "1234",
"retrievalReferenceNumber": "1234"
},
"context": "ProximityPayment",
"method": "ContactlessChipWithPin"
}🔗()Callback CardOperationCreatedOrUpdated
Settlement
Use the cardOperationId created before.
Offline operation
{
"cardId": "card_75122-1703148094663_1",
"amount": {
"value": "12.12",
"currency": "EUR"
},
"operationDate": "2024-04-16T07:23:36.915Z",
"direction": "Debit", // Debit Credit
"merchantName": "Discraft Disc",
"merchantCategoryCode": "5941"
}Complex simulation using PISO messages
For these simulations, ask your Customer Integration manager to provide you with the JSONs.They will enable you to generate the following cases:
- Authorisation with modification of
merchantCategoryCode,processingCode,context - DAC authorisation
- Authorisation with partial or total adjustment
Updated 4 months ago
Did this page help you?