No momento, esta página não está disponível em português

Autonomous stores

Use Adyen payment terminals to process payments and grant access to unattended stores.

Autonomous stores are stores without staff or checkout. A shopper presents their card to the payment terminal before entering to pre-authorize a certain amount and gain entry. They then take the items and leave the store. The purchase amount is adjusted and charged to the card that they used to enter the store.

How it works:

You make a card acquisition request on the terminal to get the card details.
The shopper presents their card to the payment terminal.
You use identifiers from the card acquisition response to check if you recognize the shopper. If it is a first-time shopper, you collect their details like phone number or email. You can use card identifiers to tokenize the card for future recurring payments.
You send a payment request to pre-authorise an amount.
We recommend that you also tokenize the card for future recurring payments. This enables you to recover failed payments in case of failed transactions.
The shopper enters the store, takes items, and leaves the store.
If the purchase amount is different from the pre-authorised amount, you send an authorisation adjustment request, followed by a capture request.
If the authorisation adjustment fails for any reason, you can capture the pre-authorized amount. After that:
- If you tokenized the card, you can make a recurring online payment for the remaining amount.
- If you collected the shopper's email or phone number, you can send them a payment link for the remaining amount.

If you cannot charge the shopper for their purchase, you can put the card alias on the not-allowed list in your system to prevent the card from being used to enter the store again.

Before you begin

Before you configure the autonomous stores flow:

Make sure that you have built an integration that can make a payment.
Before implementing pre-authorisation and adjustment, check the availability with the card issuer, the validity of the pre-authorisation request, and contact our POS Support Team to configure your payment methods.
Set up webhooks. You will need to rely on webhooks to know if the capture succeeded. If you use asynchronous authorisation adjustment, you will also need to rely on webhooks for the authorisation adjustment result.
Generate an API key. To adjust the authorisation and finalize the pre-authorised payment, you need to have an API key.

If you are using cloud-based communications, you can use the existing API key that you use for Terminal API requests.
If you plan to use the synchronous authorisation adjustment, ask our POS Support Team to enable this for you.
Make sure that you have selected a terminal model suitable for use in unattended environments: P400 Plus or UX300.

Also be aware that you need to implement logic on your end, for example how to trigger card acquisition requests on the terminal, open the doors, or calculate the amount when you make an authorisation adjustment.

Step 1: Get card details

In your back-end, implement a trigger for the card acquisition request on the terminal to prompt the shopper to present a card. From the response, you can take certain details such as the card alias to determine if the shopper should be let in.

Create a SaleToPOIData JSON object with:
- Operation.Type: Payment
- Operation.Variant: PreAuthToEnterShop. Hides the pre-authorization amount specified in CardAcquisitionTransaction.TotalAmount from showing on the initial screen. This is to prevent shoppers from thinking they need to pay to enter the store.
Operation JSON object
{ "Operation":[ { "Type":"Payment", "Variant":"PreAuthToEnterShop" } ] }
https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#operation-json-object
Encode the Operation JSON object to Base64. You will pass the resulting string in SaleData.SaleToPOIData.
Converted to a Base64-encoded string
ewogICAiT3BlcmF0aW9uIjpbCiAgICAgIHsKICAgICAgICAgIlR5cGUiOiJQYXltZW50IiwKICAgICAgICAgIlZhcmlhbnQiOiJQcmVBdXRoVG9FbnRlclNob3AiCiAgICAgIH0KICAgXQp9
https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#converted-to-a-base64-encoded-string
Create a SaleToAcquirerData JSON object with:
- authorisationType: PreAuth. Pre-authorises the amount specified in CardAcquisitionTransaction.TotalAmount.
- recurringProcessingModel: UnscheduledCardOnFile. Enforces cardholder authentication during pre-authorisation (if configured by our POS Support Team). To tokenize the card, include this field in both the card acquisition and the follow-up pre-authorisation payment request.
  
  If the PSD2 SCA compliance rules apply to your business, we recommend enforcing cardholder authentication. To enable this, contact our POS Support Team.
JSON object
{ "authorisationType":"PreAuth", "recurringProcessingModel":"UnscheduledCardOnFile" }
https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#json-object
Encode the JSON object to Base64. You will pass the resulting string in SaleData.SaleToAcquirerData.
Converted to a Base64-encoded string
ewogICAgImF1dGhvcmlzYXRpb25UeXBlIjoiUHJlQXV0aCIsCiAgICAicmVjdXJyaW5nUHJvY2Vzc2luZ01vZGVsIjoiVW5zY2hlZHVsZWRDYXJkT25GaWxlIgp9
https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#converted-to-a-base64-encoded-string

Make a CardAcquisitionRequest with:

CardAcquisitionRequest.SaleData:

Parameter	Required	Description
`SaleTransactionID`		An object with: `TransactionID`: your reference to identify the transaction. We recommend using a unique value. `TimeStamp`: date and time of the request in UTC format.
`TokenRequestedType`		Customer. Returns the card alias in the `TokenValue` field of the response. Note that the card alias is always returned in the `AdditionalResponse`.
`SaleToPOIData`		The Base64-encoded `Operation` JSON object from step 2.
`SaleToAcquirerData`		The Base64-encoded JSON object from step 4.

CardAcquisitionRequest.CardAcquisitionTransaction:

Parameter	Required	Description
`TotalAmount`		The transaction amount you want to pre-authorise before entering the store. This amount needs to be equal to the `TotalAmount` in the pre-authorisation request.

The example below shows a card acquisition request to get the card details:

{
    "SaleToPOIRequest":{
        "MessageHeader":{
            "ProtocolVersion":"3.0",
            "MessageClass":"Service",
            "MessageCategory":"CardAcquisition",
            "MessageType":"Request",
            "ServiceID":"1020711110",
            "SaleID":"POSSystemID12345",
            "POIID":"V400m-346403161"
        },
        "CardAcquisitionRequest":{
            "SaleData":{
                "SaleTransactionID":{
                    "TransactionID":"02072",
                    "TimeStamp":"2020-01-07T14:14:04+00:00"
                },
                "TokenRequestedType": "Customer",
                "SaleToPOIData":"ewogICAiT3BlcmF0aW9uIjpbCiAgICAgIHsKICAgICAgICAgIlR5cGUiOiJQYXltZW50IiwKICAgICAgICAgIlZhcmlhbnQiOiJQcmVBdXRoVG9FbnRlclNob3AiCiAgICAgIH0KICAgXQp9",
                "SaleToAcquirerData": "ewogICAgImF1dGhvcmlzYXRpb25UeXBlIjoiUHJlQXV0aCIsCiAgICAicmVjdXJyaW5nUHJvY2Vzc2luZ01vZGVsIjoiVW5zY2hlZHVsZWRDYXJkT25GaWxlIgp9"
            },
            "CardAcquisitionTransaction":{
                "TotalAmount": 10
            }
        }
    }
}

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#card-acquisition-request-

The example below shows a card acquisition response with an amount of EUR 10:

{
    "SaleToPOIResponse": {
        "CardAcquisitionResponse": {
            "POIData": {
                "POIReconciliationID": "1000",
                "POITransactionID": {
                    "TimeStamp": "2022-12-08T09:03:13.012Z",
                    "TransactionID": "i495001670490193006"
                }
            },
            "PaymentInstrumentData": {
                "CardData": {
                    "CardCountryCode": "056",
                    "MaskedPan": "541333 **** 9999",
                    "PaymentBrand": "mc",
                    "PaymentToken": {
                        "TokenRequestedType": "Customer",
                        "TokenValue": "F415978638738822"
                    },
                    "SensitiveCardData": {
                        "ExpiryDate": "0228"
                    }
                },
                "PaymentInstrumentType": "Card"
            },
            "Response": {
                "AdditionalResponse": "tid=10502371&transactionType=GOODS_SERVICES&backendGiftcardIndicator=false&posadditionalamounts.originalAmountValue=1000&expiryYear=2028&alias=F415978638738822&giftcardIndicator=false&posAmountGratuityValue=0&paymentMethodVariant=mc&applicationPreferredName=mc%20en%20gbr%20gbp&store=BookStore&aliasType=Default&cardType=mc&iso8601TxDate=2022-12-08T09%3a03%3a13.012Z&posOriginalAmountValue=1000&txtime=10%3a03%3a13&paymentMethod=mc&txdate=08-12-2022&applicationLabel=mc%20en%20gbr%20gbp&cardSummary=9999&expiryMonth=02&merchantReference=203&posadditionalamounts.originalAmountCurrency=EUR&posAuthAmountCurrency=EUR&PaymentAccountReference=fFTJzjcI35iLWvHWIYrjuUmgFMqi9&message=CARD_ACQ_COMPLETED&cardIssuerCountryId=056&posAmountCashbackValue=0&posEntryMode=CLESS_CHIP&cardBin=541333&cardScheme=mc&issuerCountry=BE&posAuthAmountValue=1000",
                "Result": "Success"
            },
            "SaleData": {
                "SaleTransactionID": {
                    "TimeStamp": "2022-11-17T12:30:21.725Z",
                    "TransactionID": "203"
                }
            }
        },
        "MessageHeader": {...}
    }
}

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#card-acquisition-response

From the CardAcquisitionResponse, save the following details :
- POIData.POITransactionID: since you are continuing with a payment, keep the TimeStamp and the TransactionID because you need these card acquisition details in your payment request.
- Response.AdditionalResponse.alias: this is a value that uniquely represents the shopper's card number (PAN), for example A37317672402294. With this, you can recognize the card that a shopper is using and identify if they are returning customers. You cannot use the card alias for making payments.
The format of the AdditionalResponse can be a Base64-encoded or URL-encoded. To always receive the AdditionalResponse in one of those formats, contact our POS Support Team.

If the shopper is entering the store for the first time, we recommend you collect their details. Otherwise, you can proceed with a pre-authorisation payment request.

Step 2 (optional): Ask for shopper's details

If the shopper is entering the store for the first time, you can ask them to enter their contact details, or to provide consent to tokenize their card.

Ask the shopper's consent to save their details. For this, you can use confirmation or signature input requests.
Collect the shopper's contact details. For this you can use phone number or text input requests. You can then use these details when tokenizing the card or to send the shopper a payment link.
Save the shopper's contact details and the card alias received in the Response.AdditionalResponse.alias of the card acquisition response.

You can use the card alias to recognize the shopper the next time they present their card to enter the store. This way, the shopper does not have to enter their details again.

Step 3: Pre-authorise an amount

After you collect the card and shopper details, send a payment request to pre-authorise the amount specified in the card acquisition request.

You can also tokenize the card with Adyen. This enables recurring payments with the shopper's card and allows you to recover failed payments in case the shopper has insufficient funds at the time of purchase.

If you plan to tokenize the card, make sure that you enable receiving shopper identifiers and check with our POS Support Team if your account is correctly configured for your tokenization use case.

Inside SaleData.SaleToAcquirerData, flag this as a pre-authorisation request. Include:
- authorisationType: PreAuth: indicates this is a pre-authorisation request.
- To tokenize the card, in the SaleData.SaleToAcquirerData also include:
  - shopperReference: your unique reference for this shopper (minimum length three characters).
  - recurringProcessingModel: UnscheduledCardOnFile. Creates a recurring contract for transactions that occur on a non-fixed schedule and/or have variable amounts. Enforces cardholder authentication (if configured by our POS Support Team).
  - shopperEmail: optional. The shopper's email address, if you collected that in the previous step.
  Pass the SaleData.SaleToAcquirerData value in one of the following formats:
  - Option 1: a JSON object converted to a Base64-encoded string. Refer to Add information to a payment. For example:
    JSON object
    
    { "authorisationType": "PreAuth", "recurringProcessingModel": "UnscheduledCardOnFile", "shopperReference": "YOUR_UNIQUE_SHOPPER_ID", "shopperEmail": "S.Hopper@example.com" }
    https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#json-object
    Encode the Operation JSON object to Base64.
    Converted to a Base64-encoded string
    
    ewogICAgImF1dGhvcmlzYXRpb25UeXBlIjogIlByZUF1dGgiLAogICAgInJlY3VycmluZ1Byb2Nlc3NpbmdNb2RlbCI6ICJVbnNjaGVkdWxlZENhcmRPbkZpbGUiLAogICAgInNob3BwZXJSZWZlcmVuY2UiOiAiWU9VUl9VTklRVUVfU0hPUFBFUl9JRCIsCiAgICAic2hvcHBlckVtYWlsIjogIlMuSG9wcGVyQGV4YW1wbGUuY29tIgp9
    https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#converted-to-a-base64-encoded-string
  - Option 2: form-encoded key-value pairs (using & as a separator). For example:
    Form-encoded key-value pairs
    
    recurringProcessingModel=UnscheduledCardOnFile&shopperReference=12345&shopperEmail=S.Hopper@example.com
    https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#form-encoded-key-value-pairs
  The format of the SaleToAcquirerData, Base64-encoded or key-value pairs, determines the format of the AdditionalResponse that you receive. To always receive the AdditionalResponse in one of those formats, contact our POS Support Team.

Make a pre-authorisation PaymentRequest with:

PaymentRequest: the request body. This includes:

Parameter	Required	Description
`SaleData.SaleTransactionID`		An object with: `TransactionID`: your reference to identify a payment. We recommend using a unique value per payment. `TimeStamp`: date and time of the request in UTC format.
`PaymentTransaction.AmountsReq`		An object with: `Currency`: the transaction currency. `RequestedAmount`: the pre-authorized transaction amount. This amount needs to be equal to the `TotalAmount` in the card acquisition request.
`PaymentData.CardAcquisitionReference`		An object referring to the card acquisition: `TimeStamp`: The time stamp returned in the `POIData.POITransactionID` of the card acquisition response. `TransactionID`: the transaction ID returned in the `POIData.POITransactionID` of the card acquisition response.
`SaleData.SaleToAcquirerData`		The Base64-encoded JSON object or form-encoded key-value pairs from step 1.

The following example shows how to pre-authorise a payment of EUR 10:

{
    "SaleToPOIRequest":{
        "MessageHeader":{
            "ProtocolVersion":"3.0",
            "MessageClass":"Service",
            "MessageCategory":"Payment",
            "MessageType":"Request",
            "SaleID":"POSSystemID12345",
            "ServiceID":"0207111104",
            "POIID":"V400m-346403161"
        },
        "PaymentRequest":{
            "SaleData":{
                "SaleTransactionID":{
                    "TransactionID":"27908",
                    "TimeStamp":"2019-03-07T10:11:04+00:00"
                },
                "SaleToAcquirerData":"authorisationType=PreAuth&recurringProcessingModel=UnscheduledCardOnFile&shopperReference=YOUR_UNIQUE_SHOPPER_ID&shopperEmail=S.Hopper@example.com"
            },
            "PaymentTransaction":{
                "AmountsReq":{
                    "Currency":"EUR",
                    "RequestedAmount":10.00
                }
            },
            "PaymentData":{
                "CardAcquisitionReference":{
                    "TimeStamp":"2022-12-15T14:53:52.977Z",
                    "TransactionID":"CglQ001671116032011"
                }
            }
        }
    }
}

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#pre-authorisation-request-with-form-encoded-key-value-pairs

The customer presents their card to the payment terminal. If the pre-authorisation is successful, Approved shows on the screen.

From the response, save the following details:

For	Use these parameters
Authorisation adjustment and capture	`POIData.POITransactionID.TransactionID`: transaction identifier for the payment, in the format Tender_reference.PSP_reference. `Response.AdditionalResponse.pspReference`: the PSP reference of your pre-authorisation request.
Calculating the amount for the authorisation adjustment	`PaymentResult.AmountsResp`: the `AuthorizedAmount` and `Currency` of the pre-authorised payment. `Response.AdditionalResponse.authorisedAmountValue`: the pre-authorised amount in minor units.
Synchronous authorisation adjustment	`Response.AdditionalResponse.adjustAuthorisationData`: a blob with authorisation data, if the synchronous flow is enabled for your account.

For easier shopper recognition and recovering failed payments, from the Response.AdditionalResponse save the following details:

Parameter	Description
`alias`	The card alias. Also returned in `PaymentResult.PaymentInstrumentData.PaymentToken.TokenValue` if the request contains `TokenRequestedType`: Customer.
`PaymentAccountReference`	A value that represents the payment account that the card and/or NFC wallet is linked to.
`recurring.recurringDetailReference`	The token representing the shopper's payment method.
`recurring.shopperReference`	Your unique reference for this shopper.
`shopperEmail`	The shopper's email address .

The following example shows the response to a EUR 10.00 pre-authorisation request.

{
    "SaleToPOIResponse": {
        "PaymentResponse": {
            "POIData":
                "POITransactionID": {
                    "TimeStamp": "2019-12-04T13:56:26.000Z",
                    "TransactionID": "8ha5001575467786000.KHQC5N7G84BLNK43"
                   }
                {...},
            "SaleData": {...},
            "PaymentReceipt": [...],
            "PaymentResult": {
                "AuthenticationMethod": [...],
                "OnlineFlag": true,
                "PaymentInstrumentData": {
                    "CardData": {
                        "EntryMode": [
                            "Contactless"
                        ],
                    "{hint:This is the card alias, not the token for future payments}PaymentToken{/hint}": {
                        "TokenRequestedType": "Customer",
                        "TokenValue": "M469509594859802"
                    },
                    "PaymentBrand": "mc",
                    "MaskedPan": "541333 **** 9999",
                    "SensitiveCardData": {
                        "CardSeqNumb": "83",
                        "ExpiryDate": "0228"
                    }
                },
                "PaymentInstrumentData": {...},
                "AmountsResp": {
                    "AuthorizedAmount": 10.00,
                    "Currency": "EUR"
                }
            },
            "Response": {
                "Result": "Success",
                "AdditionalResponse": "...adjustAuthorisationData=BQABAQA+fbc==...&alias=M469509594859802...recurring.recurringDetailReference=7219687191761347&recurring.shopperReference=YOUR_UNIQUE_SHOPPER_ID...&shopperReference=YOUR_UNIQUE_SHOPPER_ID&shopperEmail=S.Hopper%40gmail.com..."
            }
        },
        "MessageHeader": {...}
    }
}

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#pre-authorisation-response

Note that the PaymentToken object contains the card alias. You cannot use this for making payments. It is intended only for recognizing the card.

After a successful pre-authorisation, you need to have logic implemented to open the door of the autonomous store. The shopper then enters the store, takes items, and leaves.

Step 4: Adjust the pre-authorised amount

If the purchase amount for items that shopper has taken differs from the pre-authorised amount, you need to send an authorisation adjustment request. This is not a Terminal API request to the terminal itself or the Cloud endpoint for the terminal.
Depending on your infrastructure and implementation, you may want to use the asynchronous or synchronous authorisation adjustment.

When building or testing the flow, make sure there is at least a 5 second delay between the pre-authorisation and the authorisation adjustment.

Make a POST request to the /payments/{paymentPspReference}/amountUpdates endpoint, specifying:

The path with:

Parameter Required Description

paymentPspReference The pspReference of the pre-authorisation request. You received this in the response to your pre-authorisation request.
The request header with:

Parameter Required Description

content-type application/json

x-api-key Your API key.

The request body with:

Parameter	Required	Description
`amount`		The `currency` and `value` of the new amount in minor units. This is the sum of the pre-authorised amount and the additional amount. If this is not the first authorisation adjustment, it is the sum of the pre-authorised amount plus all additional amounts.
`reason`		DelayedCharge
`reference`		Your reference to this payment modification, for use in your reconciliation process.
`merchantAccount`		The name of your merchant account that is used to process the payment.

The following example shows how to add a charge of EUR 4.15 to a pre-authorised amount of EUR 10.00.

curl https://checkout-test.adyen.com/v69/payments/KHQC5N7G84BLNK43/amountUpdates \
-H "x-API-key: YOUR_X-API-KEY" \
-H "content-type: application/json" \
-d '{
        "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
        "amount": {
            "currency":"EUR",
            "value":1415
        },
        "reason":"DelayedCharge",
        "reference":"YOUR_UNIQUE_REFERENCE"
    }'

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#asynchronous-authorisation-adjustment-request

The /payments/{paymentPspReference}/amountUpdates response contains:

pspReference: The PSP reference associated with this /payments/{paymentPspReference}/amountUpdates request. Note that this is different from the PSP reference associated with the pre-authorisation request.
status: received

{
  "merchantAccount": "YOUR_MERCHANT_ACCOUNT",
  "paymentPspReference": "KHQC5N7G84BLNK43",
  "pspReference": "NC6HT9CRT65ZGN82",
  "reference": "YOUR_UNIQUE_REFERENCE",
  "status": "received",
  "amount": {
      "currency": "EUR",
      "value": 1415
  }
}

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#asynchronous-authorisation-adjustment-response

Wait for the asynchronous webhook. This informs you whether the new amount has been authorised.

If this is the first adjustment after the pre-authorisation:
- If you received the AdditionalResponse in the initial Terminal API payment response as key-value pairs separated by ampersands (&), URL-decode the value of the adjustAuthorisationData key.
  
  To find a tool or instructions for URL-decoding, search the internet for <YOUR_PROGRAMMING_LANGUAGE> decode x-www-form-urlencoded.
- If you received the AdditionalResponse in the initial Terminal API payment response as a Base64-encoded string, Base64-decode the string and copy the value of the adjustAuthorisationData field.
For adjustments after the first adjustment, skip the above step.

Make a POST request to the /adjustAuthorisation endpoint, specifying:

The request header with:

Parameter Required Description

content-type application/json

x-api-key Your API key.

The request body with:

Parameter	Required	Description
`originalReference`		The `pspReference` of the pre-authorisation request. You received this in the response to your pre-authorisation request.
`modificationAmount`		The `currency` and `value` of the new amount in minor units. This is the sum of the pre-authorised amount and the additional amount. If this is not the first authorisation adjustment, it is the sum of the pre-authorised amount plus all additional amounts.
`additionalData.adjustAuthorisationData`		The previous `adjustAuthorisationData` blob. For the first adjustment, that is the blob you received in the response to the pre-authorisation request. You need to decode that first. For the second adjustment, it is the blob you received in the response to the first adjustment, and so on. Always use the latest blob.
`reference`		Your reference to this payment modification, for use in your reconciliation process.
`merchantAccount`		The name of your merchant account that is used to process the payment.

The following examples shows how to add a charge of EUR 4.15 to a pre-authorised amount of EUR 10.00.

curl https://pal-test.adyen.com/pal/servlet/Payment/v68/adjustAuthorisation \
-H "x-API-key: YOUR_X-API-KEY" \
-H "content-type: application/json" \
-d '{
        "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
        "originalReference":"KHQC5N7G84BLNK43",
        "modificationAmount": {
            "currency":"EUR",
            "value":1415
        },
        "reference":"YOUR_MODIFICATION_REFERENCE",
        "additionalData":{
            "adjustAuthorisationData":"BQABAQA+fbc==..."
        }
    }'

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#synchronous-authorisation-adjustment-request

The /adjustAuthorisation response contains:
- additionalData.adjustAuthorisationData: the new blob, for the new authorised amount. This blob is not URL-encoded.
- merchantReference: your reference to this payment modification, for use in your reconciliation process. We recommend using the reference from the response in the previous step.
- pspReference: the PSP reference associated with this /adjustAuthorisation request. Note that this is different from the PSP reference associated with the pre-authorisation request.
- response: Authorised. Indicates the new amount is authorised.
Synchronous authorisation adjustment response
{ "additionalData": { "adjustAuthorisationData": "BQABAQArqht7L...", "merchantReference": "YOUR_MODIFICATION_REFERENCE" }, "pspReference": "NC6HT9CRT65ZGN82", "response": "Authorised" }
https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#synchronous-authorisation-adjustment-response
Store the adjustAuthorisationData blob you received in the /adjustAuthorisation response. You will need this if you later adjust the authorisation again. This blob is not URL-encoded, so you can use it as-is.

Step 5: Capture the amount

After you make the authorisation adjustment, capture the payment manually to ensure the reserved funds are transferred to your account.

Make a POST request to the /payments/paymentPspReference/captures endpoint, specifying:

The path with:

Parameter	Required	Description
`paymentPspReference`		The `pspReference` of the authorisation being captured. You received this as part of the `transactionID` field in the response to your payment request. See Transaction identifier.

The request header with:

Parameter Required Description

content-type application/json

x-api-key Your API key.

The request body with:

Parameter	Required	Description
`amount`		The `currency` and `value` of the final amount in minor units. This is the sum of the original, pre-authorised amount and all later adjustments.
`reference`		Your reference to this payment modification, for use in your reconciliation process.
`merchantAccount`		The name of your merchant account that is used to process the payment.

curl https://checkout-test.adyen.com/v68/payments/KHQC5N7G84BLNK43/captures \
-H 'x-api-key: YOUR_API_KEY' \
-H 'content-type: application/json' \
-d '{
       "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
       "amount":{
          "currency":"EUR",
          "value":1415
       },
       "reference":"YOUR_UNIQUE_REFERENCE"
}'

https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#capture-request

When you receive the capture response, note the following:
- pspReference: the PSP reference associated with this capture request. Note that this is different from the PSP reference associated with the pre-authorisation request.
- status: received.
- reference: your reference to this payment modification, for use in your reconciliation process.
Capture response
{ "reference": "YOUR_MODIFICATION_REFERENCE", "pspReference": "QJ7GWQ756L2GWR86", "status": "received" }
https://docs.adyen.com/pt/pt/point-of-sale/autonomous-stores#capture-response
Wait for the asynchronous webhook. This informs you whether the final amount has been captured.
If the capture is successful, this webhook contains:
- eventCode: CAPTURE
- originalReference: The pspReference of the pre-authorisation.
- pspReference: The PSP reference associated with this capture request.
- success: true
If success is false then your capture request failed. Review the reason you received in the webhook, fix the issue, and submit the capture request again.

Recover failed payments

If the authorisation adjustment fails for any reason, for example because of a technical issue or insufficient funds on the cardholder’s bank account, there are several things you can do:

Send the capture request to collect the pre-authorised amount.
Make a recurring online payment for the remaining amount using the token you created in the pre-authorisation payment request.
Send a payment link for the remaining amount to the shopper's email or phone number that you collected before the shopper entered the store.

You can also enable our Auto Rescue feature that automatically retries shopper-not-present card transactions when they are refused.

If all rescue attempts fail, you can put the card alias on the not-allowed list in your system to prevent the card from being used to enter the store again.

Are you looking for test card numbers?

Would you like to contact support?

Autonomous stores

Before you begin

Step 1: Get card details

Step 2 (optional): Ask for shopper's details

Step 3: Pre-authorise an amount

Step 4: Adjust the pre-authorised amount

Step 5: Capture the amount

Recover failed payments

See also