---
schema_version: "1"
id: 64cd17ad4f814acbdd5318661d153d99d34cdc74eb8018dd8a8aa58df484527e
title: Adyen Payment Gateway Information
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_cms_hardware_ayden_gateway_info.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_ayden_gateway_info.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 1b0986fb003db2ab389fe17ffefe5967f64bc82a105f427f11efba3c65067df9
description: You can configure different payment gateways at the store level, such as store-level settlements, reporting, and currency requirements and integrate Adyen into Point of Sale.
products:
  - Commerce
release: "264"
---
# Adyen Payment Gateway Information

You can configure different payment gateways at the store level, such as store-level settlements, reporting, and currency requirements and integrate Adyen into Point of Sale.

Before you start the configuration process, have this information ready:

- **Admin Access** — If providing admin access, then provide the account name, username, and password.
- **No Admin Access** — If not providing admin access, then provide the admin menu pin, transaction menu pin, and maintenance menu pin.
- **iOS SDK (e315 Only)** — If using the iOS SDK, then provide a Web service username and password. As of 2022, Adyen doesn’t support ‌the e315 device.
- **Terminal API** — If using the terminal API, then provide the encryption version, identifier, and passphrase.

![Adyen Portal's General Settings screen.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_ayden_payment_gateway.png)

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png)

Note

Amex requires separate merchant IDs (MIDs) for ecommerce and Point of Sale (POS). Visa, Mastercard, and so on don't require separate MIDs.

## Creating a Configuration for Adyen

1. Go to **Integrations > Payment Gateways**.
2. Select **CREATE**.
3. Under **Payment Gateway**, select **Adyen** from the dropdown.
4. Log into your Adyen Console and select the right merchant account.
5. Fill out all required fields using the table.
6. Select **SAVE** to save your changes.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
            <colgroup>
              <col style="width:25%">
              <col style="width:25%">
              <col style="width:25%">
              <col style="width:25%">
            </colgroup>
            <thead class="slds-text-title_caps ">
              <tr class="">
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d162359e177">Field</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d162359e180">Field Type</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d162359e183">Required</th>
                <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d162359e186">Description</th>
              </tr>
            </thead>
            <tbody>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">General Settings</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Payment Gateway</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pulldown</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Type of payment gateway (for example Adyen) </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Environment</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pulldown</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Environment of the account (for example Test)</p>
                  <p style="margin-bottom:0;">To test contactless payments, use a card version of 2.4 or newer.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Fulfillment Type</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pulldown</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Fulfillment type— select Default if you want to create this configuration for a POS
                  app to perform transactions</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Store ID</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pulldown</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Select a particular store from the store dropdown to apply these settings to a
                    particular store (for example, 1).</p>
                  <ul>
                    <li>
                      <p>If you've yet to set up an Adyen and Point of Sale account, make sure your StoreIDs
                        are the same for both accounts.</p>
                    </li>

                    <li>
                      <p>If your Point of Sale account is live but you haven’t set up Adyen, make sure your
                        Adyen StoreID is the same as your Point of Sale StoreID.</p>
                    </li>

                    <li>
                      <p>If your Adyen account is live but you haven’t set up Point of Sale, make sure your
                        Point of Sale StoreID is the same as Adyen's StoreID.</p>
                    </li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Payment Method</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pulldown</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>To distinguish between debit and credit card payments, you will need to turn on that
                    with your Adyen representative (for example, Credit Card)</p>
                  <p style="margin-bottom:0;">For debit cards, refer to the Field Funding Source in your Adyen terminal account.
                    Additionally, turn on Funding Sources and Return Parameters in Adyen. </p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Additional Payment Method</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pull down</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">This enables finance options to be processed on the POS app. <a href="https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_3p_int_finance_synchrony.htm&amp;release=264.0.0&amp;type=5" title="The POS app, in combination with an Adyen terminal, supports the recognition of Synchrony cards and enables financing transactions. During checkout, when a customer chooses to pay with their Synchrony PLCC and the card is presented, the store associate can process the payment. If the order total meets a set threshold, the store associate can offer financing, which requires the customer to sign an electronic disclosure and financing contract. The threshold, electronic disclosure, and financing contract terms are customizable in the CMS."><u>Learn
                      More</u></a></td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Device ID</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Device ID that needs to be associated with this configuration. Irrelevant for Adyen
                  and set to Default</td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Connectivity and Authentication</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">URL Base</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>URL base for refunds and other communications to Adyen Cloud from Point of Sale.
                    Reach out to your Adyen representative </p>
                  <p><u>Test:</u> https://pal-test.adyen.com/pal/servlet/Payment/[version]</p>
                  <p><u>Live:</u>
                    https://[prefix]-pal-live.adyenpayments.com/pal/servlet/Payment/[version]</p>
                  <p>For example https://pal-test.adye-n.com/pal/servlet/</p>
                  <p style="margin-bottom:0;">Payment/V52 </p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Secondary URL Base</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Adyen will sunset Classic Payment APIs on March 31, 2024. Use the secondary URL base.</p>
                  <p><u>Test:</u> https://checkout-test.adyen.com/checkout/v71</p>
                  <p style="margin-bottom:0;"><u>Live:</u> https://{PREFIX}-checkout-live.adyenpayments.com/checkout/v71</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Merchant Gateway ID</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Name of the merchant account (for example POS)</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">
                  <p>Merchant Key</p>
                  <p style="margin-bottom:0;">(API Key in Adyen Console)</p>
                </td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">API Key used by Point of Sale for all their API communication and POS for Pay By Link
                  and Terminal Management. It can be found by going to Developers &gt; Account Credentials.
                  Check if you have a Web service user available. If not, reach out to Adyen Support to
                  request a Web service user. Select the Web service user. In the Authentication section,
                  you’ll see the API Key section. </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Services</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Checkbox</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Services associated with the payment gateway. POS uses only Mail Order Telephone
                  Order (MOTO).</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Verify</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Button</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">After you've entered all the necessary information to connect your payment gateway
                  service to Point of Sale, select the button to verify a successful connection. An error
                  message will display if any of the information is incorrect. This verification process is
                  also done.</td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Terminal Configuration</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Certificate Name Suffix</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Auto-Complete</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Terminal certificate name suffix associated with the payment gateway (for example,
                  terminal.adyen.com)</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Gateway ID</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Merchant gateway ID associated with the terminals (for example, merchantPOS). POS
                  uses this for Terminal Connection Validation. It is also used for defining the merchant
                  codes if requesting for Terminal Management and Pay By Link.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Key Identifier</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The key identifier in the Encryption Key section; used for API communication with
                  terminals. </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Key Encryption Version</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The key version in the Encryption Key section; used for API communication with
                  terminals.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">
                  <p>Terminal User Name</p>
                  <p style="margin-bottom:0;">(Username in Adyen Console)</p>
                </td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>The Web service username used to register the Adyen SDK for Legacy Terminal.</p>
                  <p style="margin-bottom:0;">Important: Support is no longer available for this field. </p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Key Passphrase</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The key passphrase in the Encryption Key section; used for API communication with
                  terminals.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Beacon ID</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>The terminal beacon ID. Setting this value will allow a terminal connection via beacons
                    before each transaction. This will also disconnect the terminal after the order
                    completion.</p>
                  <p style="margin-bottom:0;">Important: Support is no longer available for this field. </p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Terminal Request Timeout Interval in Seconds</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The terminal request timeout. Using ‌low values can cause problems. 150 seconds is
                  the recommended default value. Negative values aren't allowed.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Payment Tokenization Events</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Pulldown</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Select when to tokenize payment methods for later use. Select "Endless Aisle" to tokenize online portions of mixed carts (orders containing both in-store and Endless Aisle items).</p>
                  <div class="slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium">
                    <div class="slds-media slds-media_responsive">
                      <div class="slds-media__figure"><span class="slds-icon_container slds-icon_container_circle slds-icon-note-note"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png" alt="Note"></span></div>
                      <div class="slds-media__body" style="padding-top:.5rem;padding-bottom:.5rem;"><span class="slds-text-title_caps">Note</span>
                        <p>If an Endless Aisle order cancels before online fulfillment, the merchant's OMS is responsible for sending a cancellation for the authorized amount and token to Adyen.</p>
                      </div>
                    </div>
                  </div>
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Payment Status Verification </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Payment Status Check API Timeout in Seconds</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The payment status check API timeout. The minimum interval is 5 seconds, and it can
                  be adjusted up to 150 seconds based on the store's network quality. Setting the interval
                  too short doesn’t give the terminal sufficient time to process and respond. </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Transaction Verification Days</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Retention period for verifying unverified transaction in days</td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Advanced</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Skip Fraud Check</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Turn on this feature if you want to skip the risk engine for Adyen transactions.
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Has Cart Summary On Payment Terminal</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Turn on this feature if you want to have the cart summary on the payment
                  terminal.</td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Manual Payment Settings</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Manual Credit Card Entry on Terminal</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Turn on this feature if you want to have manual credit card entry on the payment
                  terminal.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Manual Payment Capture</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Turn on this feature if you want to turn on manual payment capture. Refer to this
                  <a href="https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_config_auth_mode_payments.htm&amp;release=264.0.0&amp;type=5" title="Use the Point of Sale (POS) app to authorize payments for Endless Aisle or Online transactions and collect money whenever items are sent to customers."><u>article</u></a> to learn more about configuring capture payments.
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Mixed Cart Payment: Partial Capture</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Turn on to capture in-store portions of mixed carts immediately while keeping online
                    portions authorized. The app captures the online portion when the order ships. Works with
                    Payment Tokenization Events set to "Endless Aisle".</p>
                  <div class="slds-box slds-box_x-small slds-theme_shade slds-m-top_medium slds-m-bottom_medium">
                    <div class="slds-media slds-media_responsive">
                      <div class="slds-media__figure"><span class="slds-icon_container slds-icon_container_circle slds-icon-note-warning"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png" alt="Important"></span></div>
                      <div class="slds-media__body" style="padding-top:.5rem;padding-bottom:.5rem;"><span class="slds-text-title_caps">Important</span>
                        <p>Don't turn on Mixed Cart Payment: Partial Capture if you use Edit Order. Combining these
                          features creates a critical vulnerability in the refund flow that can lead to revenue loss
                          or payment abuse.</p>
                      </div>
                    </div>
                  </div>
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Terminal Management Settings</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Adyen Company Account Name</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The Adyen company account name.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Adyen Store Code</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Adyen store code, which can be found by going to "In-person payments" -&gt; Stores. For
                    example, the Adyen store code is "001".</p>
                  <p style="margin-bottom:0;">Required for Tap to Pay if you’ve set up store-level payment settings in Adyen. For example, if certain payment methods are only available at specific stores, each of those stores must have an Adyen Payment Gateway configured in CMS with the correct Adyen Store Code.</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Adyen Merchant Management URL Prefix</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>The merchant's URL prefix.</p>
                  <ul>
                    <li>
                      <p><u>Test:</u> https://management-test.adyen.com/v3 </p>
                    </li>

                    <li>
                      <p><u>Live:</u> https://management-live.adyen.com/v3</p>
                    </li>

                  </ul>
                  <p>The Management API permissions must be granted on your Adyen console for these
                    endpoints:</p>
                  <ul>
                    <li>
                      <p>/terminals: Management API - Terminal actions read</p>
                    </li>

                    <li>
                      <p>/stores: Management API - Stores read, Management API - Stores read and write</p>
                    </li>

                    <li>
                      <p>/terminalSettings: Management API - Terminal settings read, Management API - Terminal
                        settings read and write</p>
                    </li>

                  </ul>
                  <p style="margin-bottom:0;"><em>If any of the previous permissions aren't displayed in the console, reach out to
                      Adyen support to have them turned on and displayed.</em></p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Adyen Terminal Management URL Prefix (Deprecated)</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>Adyen’s POS Terminal Management API is being deprecated with a planned sunset date of
                    April 1, 2025. As the Management API is used instead, the merchant’s URL prefix should be
                    provided in the new "<em>Adyen Merchant Management URL Prefix</em>" field in this Payment
                    Gateway Configuration.</p>
                  <ul>
                    <li>
                      <p><u>Test:</u> https://postfmapi-test.adyen.com/postfmapi/terminal/v1</p>
                    </li>

                    <li>
                      <p><u>Live:</u> https://postfmapi-live.adyen.com/postfmapi/terminal/v1</p>
                    </li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Tap to Pay Settings</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Adyen Tap to Pay URL</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>The URL endpoint that is used to create a payment session for the app.</p>
                  <ul>
                    <li>
                      <p><u>Test:</u> https://checkout-test.adyen.com/possdk/[version]</p>
                    </li>

                    <li>
                      <p>Live: https://[prefix]-checkout-live. adyenpayments.com/checkout/ possdk/[version]</p>
                    </li>

                  </ul>
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Pay By Link Settings</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Pay by Link Base URL</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>The URL endpoint that is used to create a payment session for the app.</p>
                  <p><u>Test:</u> https://checkout-test.adyen.com/[version]</p>
                  <p><u>Live:</u> https://[prefix]-checkout-live.adyenpayments.com/checkout/[version]</p>
                  <p style="margin-bottom:0;">For example, https://checkout-test.adyen.com/v67</p>
                </td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Pay by Link URL Expiration in Hours</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Number</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">The Pay-By Link expiration time. The minimum expiration time is 24 hours and the
                  maximum expiration time is 1680 hours.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Send Store ID to Adyen</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Enabled means that store details are included in the payload if a payment link is
                  created using the pay by link or Remote pay by link flows.</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Require Customer's Email to be Submitted</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Enabled indicates that a customer email is required to support all Pay by Link
                  orders. Note, this must be enabled for any merchants using PBL in the EU. <a href="https://help.salesforce.com/s/articleView?id=commerce.rt_pos_checkout_adyen_pbl_eu_update.htm&amp;release=264.0.0&amp;type=5" title="For EU merchants using Pay By Link (PBL), Adyen has added three fields: Browser IP Address, Cardholder Name, and Cardholder Email Address or Cardholder Phone Number. Adyen automatically handles the Browser IP Address, but the other two require configuration in both the CMS and your Adyen account portal.">Learn More</a></td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Callback URL</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Generate Callback URL</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Other</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">
                  <p>For Salesforce to receive Adyen callbacks related to payment failures, Salesforce
                    provided a callback URL.</p>
                  <p style="margin-bottom:0;">Important: The callback URL can only be configured at either the Company or Merchant
                    level. It can't be configured in both places. <a href="https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_ayden_gateway_info.htm&amp;release=264.0.0&amp;type=5" title="Set up Adyen to process payments securely and reliably. Define the URL base, merchant gateway ID, and merchant key within Adyen to work with Point of Sale.">Learn More</a></p>
                </td>

              </tr>
              <tr class="">
                <td class="slds-cell-wrap" colspan="4" style="vertical-align:top;" headers="d162359e177 d162359e180 d162359e183 d162359e186 ">Gift Card Settings</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Enable Gift Card</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Enabled indicates that gift cards will be supported via the payment terminal</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Enable Expiry Date Input Field</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Switch</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">No</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Enabled indicates that an input field for gift card expiry date shows in the terminal
                  during gift card operations</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Gift Card Provider </td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">​Select the gift card provider that'll be used in the terminal</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Gift Card SKU</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Text</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Product ID/SKU for a gift card</td>

              </tr>
              <tr class="">
                <td data-label="Field" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e177 ">Cash Out Configuration</td>

                <td data-label="Field Type" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e180 ">Window</td>

                <td data-label="Required" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e183 ">Yes</td>

                <td data-label="Description" class="slds-cell-wrap" style="vertical-align:top;" headers="d162359e186 ">Configure cash redemption thresholds for gift cards. For more information, refer to
                  this article. </td>

              </tr>
            </tbody>
          </table>

## Turn On Cross-Store Refund Attribution for Adyen

Use this setting if your refund flow allows returns at a different store than the original purchase location, especially across different Merchant Codes. This helps makes sure the correct store information is passed to Adyen during refund transactions, helping prevent mismatches that can lead to refund issues.

1. In CMS, go to **Store Management > Store Settings**
2. Expand **Adyen**.
3. Turn on **Attribute Cross-Store Returns to the Store where Returns are Processed (crossStoreRefundWithAdyen)** (1).![The Attribute Cross-Store Returns to the Store where Returns are Processed (crossStoreRefundWithAdyen) setting turned on.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_mcs_hardware_ayden_settings_xstore_refund.png)

## Configure Ayden and Set Up Payment Gateway

Set up Adyen to process payments securely and reliably. Define the URL base, merchant gateway ID, and merchant key within Adyen to work with Point of Sale.

### Ayden Fields

**URL Base**: This is the URL base for refunds and other communications to the Adyen Cloud from Point of Sale. Reach out to your Adyen representative.

- Test: https://pal-test.adyen.com/pal/servlet/Payment/\[version\]
- Live: https://\[prefix\]-pal-live.adyenpayments.com/pal/servlet/Payment/\[version\]

**Merchant Gateway ID**: Name of the merchant account (for example RetailCloudPOS in the image). This can be found by selecting your account in the upper left corner of the screen.

![Tip](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_tip.png)

Tip Make note of whether you're in the merchant-level account or company-level account (outlined in red). [Learn More](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_ayden_gateway_info.htm&release=264.0.0&type=5 "You can configure different payment gateways at the store level, such as store-level settlements, reporting, and currency requirements and integrate Adyen into Point of Sale.")

![The Merchant Gateway ID and URL Base in the Ayden Portal.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_merchant_gateway.png)

**Merchant Key**: This is the API key used by Point of Sale. Find your merchant key by going to **Developers > API Credentials**. Check if you have a Web service user available. If not, reach out to Adyen Support to request a Web service user. Select the Web service user after it’s available. In the Authentication section, you will see the API Key section. ![The Merchant Key on the API Credentials page in Ayden Portal](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_merch_key_ayden.png)

If an API key exists, check with the account owner to see if they have the API Key. If they can't provide it, confirm with Point of Sale if a new key can be generated.

**Generating a new API Key**: Select Generate New API Key.![Generate a new API key in Ayden Portal](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_hardware_gerneate_api_key.png)

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png)

Important Copy the API Key in a safe place immediately before it is obfuscated.

After you've saved the API Key, select confirm and save the API Key.

**Terminal Gateway ID**: The merchant gateway ID associated with the terminals. POS uses this for Terminal Connection Validation. It is also used for defining the merchant codes if requesting for Terminal Management and Pay By Link.

### API Terminal Integration

1. Go to **Adyen Console > In-person payments > Terminal settings > Integrations**.
2. Turn on the terminal API. For any changes to the terminal API, make sure you're using **Decrypted** mode as it will give you full access for any edits.
3. Scroll down to the **Encryption Key** section.
4. If these fields don't exist, add new ones and select Save at the bottom:
    1. **Terminal Key Encryption Version**: Key version in the Encryption Key section; used for API communication with terminals.
    2. **Terminal Key Identifier**: Key identifier in the Encryption Key section; used for API communication with terminals.
    3. **Terminal key Passphrase**: Key passphrase in the Encryption Key section; used for API communication with terminals.

### Callback URL

For Point of Sale to receive Adyen callbacks related to payment failures, Salesforce provided a callback URL. The URL shall be at the Point of Sale Merchant - Region level. [Learn More](https://help.salesforce.com/s/articleView?id=commerce.rt_cms_hardware_ayden_gateway_info.htm&release=264.0.0&type=5 "You can configure different payment gateways at the store level, such as store-level settlements, reporting, and currency requirements and integrate Adyen into Point of Sale.")

For enabling Pay by Link (PBL) for a merchant that is under a parent company, refer to [_Callback URL for Payment Gateway Integrations_](https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_pay_gate_callback.htm&language=en_US)_._

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png)

Note Basic Authentication, HMAC key, and Additional Settings \[enabled\] aren't needed for Salesforce Adyen integration.

1. Generate a Point of Sale callback URL by going to your Point of Sale CMS staging account.
    1. Go to **Store Management > Integrations > Payment Gateways**.
    2. Edit an existing configuration or create one.
    3. Under **Callback URL**, generate a new URL and copy it.
2. Go back to your Adyen console, go to **Developers > Webhooks > + Webhoook (blue button top right) > Standard Notification - Add**.
3. (Optional) Under **Description**, enter a description for the webhook.
4. Under **Server Configuration**, paste the URL you previously generated. Make sure that the Method is "**JSON**", the Encryption protocol is "**TLSv1.2**", and **Enabled** is turned on.
5. Go to **Test Notification > Select All > Test**. Check with Salesforce if a test notification is received in their backend for the merchant in the respective environment.
6. Go to **Additional Settings > Select All > Save Configuration**.

### Recommended Account Setup

The callback URL within Adyen should be configured at the Point of Sale Merchant - Region level. Each region requires a unique payment gateway configuration, which includes a distinct callback URL. For example, a callback URL intended for the Germany (DE) region shall be exclusively associated with the corresponding DE Adyen account.

If incorrectly configured, this can cause additional callbacks from Adyen, leading to inaccurate entries (false positives) in the Failed Order report. This happens if transactions intended for one merchant are mistakenly recorded under an unrelated account that doesn'tt recognize them.

To make sure your account structure is correctly set up, consult with your Adyen representative.

## Deprecated Ayden Terminal Properties

These terminal properties for connecting to the Terminal via Beacons and Adyen SDK Integration with Point of Sale are no longer supported.

### Terminal via Beacons \[Support Deprecated\]

The following properties are required for connecting to the Terminal via Beacons:

- Go to **Adyen Console > In-person payments > Terminal Settings.**
- Select **View Decrypted** at the bottom (This will allow you to see the properties in plain text).
- Select **Connectivity**.
- Scroll down to the **Beacon** section.
    
    SDK Integration is used for legacy terminals such as the e315.
    
    Important: As of 2022, Adyen has announced the end of support for the e315 device.
    
    Terminal Beacon ID: Select Enable Beacons if not enabled. Use UUID from the Beacon section

### Adyen SDK Integration \[Support Deprecated\]

SDK Integration is used for legacy terminals such as the e315.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_important.png)

Important As of 2022, Adyen has announced the end of support for the e315 device.

Terminal Username: Name of the Web service user you used previously (for example If the name is ws@company, use WS).

Terminal Password: Select into the previous Web service user. In the Authentication section, you will see Basic Auth.

If a password exists, check with the account owner to see if they have the password. If they can't provide it, confirm with Salesforce if a new password can be regenerated.

Generating a new password:

- Type the password and retype it to confirm it.
- Copy the Password in a safe place immediately before it is obfuscated.
- Select **Generate POS Password**.
- After you've saved the Password, select **confirm** and save the Password

## Frequently Asked Questions (FAQs)

Learn about the most often-asked questions about Ayden Gateway and how it functions with Point of Sale

### How long does it take for money to be returned to a customer's card if processing a return with Adyen?

We don't support a postvoid CTA from the POS app. With Adyen, if the entire order is marked for return, our initial action is to void the order. If the payment hasn't been captured, Adyen cancels the order. If the payment has been taken, it starts the normal refund process. This usually takes 3–5 business days, but this time varies by bank and institution.

### What's the typical time window for payment capture with Adyen before it cancels vs. refunds?

For in-store cash and carry, capture occurs before the Thank You screen on the POS app. For manual capture, typically during shipment. Sometimes partial capture can happen immediately. All these settings are configurable by the merchant.

### Is it possible to perform a void auth with Adyen?

We attempt a cancellation (void) with Adyen first. If it fails because the funds have been captured, we proceed with a refund. The timing of capture is entirely configurable by the merchant. Cancellation removes the authorization on the card and makes the funds available again.

### Does Adyen require canceling the entire order, or can specific lines be canceled, and can we update the authorization amount?

Yes, Adyen requires full order cancellation; specific line cancellation is not supported. Any adjustments to the authorization amount & follow the normal refund process.

### How can we mark a sale as returned if the refund was initiated in Adyen?

Currently, marking a sale as returned directly from the POS isn't possible if the refund is processed through Adyen. It is recommended to coordinate with your accounting team to manage such cases. They can make the changes they need directly in Salesforce, using the Order Management Record (MOR), instead of through the POS system. Make sure that your Finance team, if they're handling refunds via Adyen, can modify orders in your Order Management System (OMS) accordingly.

### How do I set up the POS for a merchant composed of two legal entities, each with its own bank account?

For a merchant with two legal entities and separate bank accounts, it's recommended to set up all stores from both legal entities in a single Point of Sale environment. At the store level, you can select a payment gateway (Adyen) and tie it to the respective bank account for each legal entity. Transactions from each store will be routed to the respective bank account associated with that store's legal entity. Keep in mind that store-level configuration for order posting is not supported, and each legal entity shall have its own merchant account, as per Adyen's documentation.