POST /cardreaderapdu
It contains the APDU request to send to the chip of the card, and a possible invitation message to display on the CashierInterface or the CustomerInterface. Content of the Card Reader APDU Request message.
Servers
- https://device-api-test.adyen.com/v1/merchants/{merchantAccount}/devices/{deviceId}/sync
- https://device-api-test.adyen.com/v1/merchants/{merchantAccount}/devices/{deviceId}/async
- <local-terminal-IP-address>
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
APDUInstruction |
String | Yes |
Instruction field of the APDU command (INS). |
APDUExpectedLength |
String | No |
Expected length of the data field of the APDU response to the command (Le). |
APDUClass |
String | Yes |
Class field of the APDU command (CLA). APDU request for Card Reader device request. For specific card like synchronous card, a private value should be used in accordance to ISO 7816- 4 (private range D0-FE). |
APDUPar1 |
String | Yes |
Parameter 1 field of the APDU command (P1). |
APDUData |
String | No |
Data field of the APDU command (Lc + Data). |
APDUPar2 |
String | Yes |
Parameter 2 field of the APDU command(P2). |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.