Supported Functions

Below is a list of supported functionalities of the interface to Pay by Link.

Important: Adyen are no longer accepting new customers for the Customer Present Pay By Link feature. Please discuss this directly with Adyen if further clarification is necessary.

Table 5-4 Pay By Link - Supported Functions

Function	Description
Customer not present - Payment/Payment with Loyalty	The POS initiates a customer not present pay by link tender. EFTLink sends the request to the Adyen Online Payments (Checkout API) endpoint. The Adyen Online Payments endpoint will create a payment link which EFTLink will send back to the POS. The customer will be referred to pay via the link generated by the Adyen Online Payments system. In the event of a communication failure between EFTLink and the Adyen Online Payments endpoint; the POS operator will be prompted by EFTLink as to whether they would like to Retry or Decline the transaction. Due to API Idempotency, if the operator chooses to Retry the transaction, an exact duplicate of the previous request is sent once again to the Adyen Online Payments endpoint. Should the connection timeout continue to occur, the POS operator will be continually asked whether they would like to Retry or Decline until they press the Decline button. If the operator presses the Decline button, EFTLink will simply return a failure result to the POS and the POS will return back to the tender screen.
Customer present – Payment/Payment with Loyalty	The POS initiates a customer present pay by link tender. EFTLink sends the request to the Adyen In-Store (Terminal API) Payment Entry Device (PED). The PED will display a QR code which the customer will scan and enter their card details on the secure form generated by the Adyen payment gateway. Once the customer has completed the form and the payment has been processed, EFTLink will return a response including formatted merchant/customer receipts as required. In the event of a communication failure between EFTLink and the PED an initial Transaction Status request is sent from EFTLink to determine the status of the request. If the initial Transaction Status check succeeds, the original response details will be sent from EFTLink to the POS. If the initial Transaction Status check returns as in-progress, EFTLink will continue to query the status of the transaction until a valid response is returned. Once the final response has returned, EFTLink will send the original response details back to the POS. If the initial Transaction Status check times out, the POS operator will be prompted by EFTLink as to whether they would like to Retry or Decline the transaction. If the operator chooses to Retry the transaction, EFTLink will attempt to re-send the previous Transaction Status check until a valid response is returned or until the cashier presses the Decline button when prompted after every check. If an in-progress response is returned, the in-progress scenario outlined above occurs. If a valid final response is returned, EFTLink will send the final response back to the POS and complete the transaction as usual.
Customer not present – Link Query	The POS initiates a customer not present link query request with the link Id to check the status of a link. EFTLink sends the link query request to the Adyen Online Payments (Checkout API) endpoint. The Adyen Online Payments endpoint will respond with the status of the link. EFTLink will set the status of the link in the final response to the POS. The status of the link will be one of the following: active expired completed paid
Customer not present – Link Expiry	The POS initiates a customer not present link expiry request with the link Id to expire. EFTLink sends the link expiry request to the Adyen Online Payments (Checkout API) endpoint. The Adyen Online Payments endpoint will set the status of the link to expired in the response to EFTLink. EFTLink will send the final response to the POS with the new status set.
Reversal	Customer not present reversal is possible if the POS initiates a Post Void request to EFTLink following a customer not present pay by link tender. This will simply expire the link which was generated during the initial customer not present pay by link tender. Customer present reversals behave in the same way as a reversal for any standard transaction. EFTLink converts the reversal request into a Verified Refund request using the original transaction reference and sends this request to the Adyen In-Store (Terminal API) endpoint.
Verified Refund	All verified refund requests are handled by the Adyen Online Payments (Checkout API) endpoint. The POS initiates a Verified Refund request. EFTLink sends the refund request to the Adyen Online Payments endpoint. The Adyen Online Payments endpoint responds with a valid response. EFTLink sends the final response to the POS.
Time out handling	All transactions processed by the Pay by Link core are available for the timeout scenarios described under the “Customer not present - Payment/Payment with Loyalty” and “Customer present – Payment/Payment with Loyalty” sections of this “Pay by Link – Supported Functions” table, refer to these sections for further information.