Terminal-2 icon

Turn on accessibility mode from the POS app

Make accessible payments for visually impaired shoppers from your POS app.

View source

For shoppers with visual impairments, you can turn on accessibility mode through the payment request from your POS app. The payment terminal then provides audio instructions during the payment. The payment request needs to include an encoded object to turn on accessibility mode.

Requirements

Before you begin, take into account the following requirements, limitations, and preparations.

Requirement Description
Integration type A Terminal API integration with payment terminals.
Hardware Accessibility mode is supported on Android terminal models:
  • AMS1, S1F2, S1F2L, S1E2L, S1U2 on software version 1.117 or later.
  • M450, P630, SFO1 on software version 1.124 or later.
Limitations Accessibility mode is not compatible with:
  • Tipping
  • Giving
  • Signature as a cardholder verification method
  • The following languages: Estonian, Latvian, Icelandic, and Lithuanian
Setup steps Contact our Support Team:
  • Ask them to enable accessibility mode for your terminals.
  • Tell them if you want to extend the default timeout for the payment screens (two minutes) and the PIN entry screen (five minutes).

How it works

  1. You make a payment request with a Base64-encoded Operation object to turn on accessibility mode.

  2. The terminal reads out the text shown on the terminal screen, and instructs the shopper on how to present their payment card.
    The timeout period is extended to give the shopper time to listen to the audio instructions.

  3. The shopper presents their card to complete the payment.

  4. Accessibility mode turns off automatically.

Make an accessible payment from the POS app

After accessibility mode is enabled by our Support Team, you are ready to make a payment request with a Base64-encoded Operation object to turn on accessibility mode for a specific payment.

  1. Create an Operation JSON object with the Operation.Type: Payment and Operation.Variant: EnableAccessibilityMode:

  2. Encode the Operation JSON object to Base64. You will pass the resulting string in SaleData.SaleToPOIData.

  3. Make a payment request, specifying:

    • The standard SaleToPOIRequest.MessageHeader object, with MessageClass set to Service and MessageCategory set to Payment.

      Parameter Required Description
      ProtocolVersion -white_check_mark- 3.0
      MessageClass -white_check_mark- Service
      MessageCategory -white_check_mark- Payment
      MessageType -white_check_mark- Request
      ServiceID -white_check_mark- Your unique ID for this request, consisting of 1-10 alphanumeric characters. Must be unique within the last 48 hours for the terminal (POIID) being used.
      SaleID -white_check_mark- Your unique ID for the POS system component to send this request from.
      POIID -white_check_mark- The unique ID of the terminal to send this request to. Format: [device model]-[serial number].

    • The PaymentRequest object with:

      Parameter Description
      SaleData.SaleTransactionID An object with:
      • TransactionID: your reference to identify a payment. We recommend using a unique value per payment. In your Customer Area and Adyen reports, this will show as the merchant reference for the transaction.
      • TimeStamp: date and time of the request in UTC format.
      SaleData.SaleToPOIData The Base64-encoded Operation object.
      PaymentTransaction.AmountsReq An object with:
      • Currency: the transaction currency.
      • RequestedAmount: the purchase amount, with decimals.

    The payment response is the same as with a regular payment. The terminal exits the accessibility mode after a successful or canceled payment.

See also