---
schema_version: "1"
id: 8b152cac07318498a12f91f6e4f5db337e527e1d04cd22af1c4601f81eb62a6c
title: Point of Sale Payments Frequently Asked Questions
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_adv_config_pay_gate_faq.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_adv_config_pay_gate_faq.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: a4e3b233c9a0a5bfcb46a712b86306d0fb52cf88f271a015bfaf5b37f2f758b7
description: Get answers to frequently-asked questions about payment transactions.
products:
  - Commerce
release: "264"
---
# Point of Sale Payments Frequently Asked Questions

Get answers to frequently-asked questions about payment transactions.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Scenario </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Solution</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">What payment gateways are supported?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Adyen and Elavon are available. All others need custom development and scoping.
            For any new payment adaptor, the timeline is six to ten weeks.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Can I have two Adyen payment gateway integrations for facilitating e-commerce and
            in-store orders?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">This will not work at a store level as we only support one payment gateway. We do
            not have a provision to add a separate store for e-commerce orders unless that is
            created as a stand-alone store to do transactions with different gateway
            settings.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Do you support auth-only on POS?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Yes, Adyen can be configured to perform auth-only for the online part of endless
            aisle order and sale for in-store portion.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Where is payment token stored?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Point of Sale stores the authorization/capture token provided by payment gateway
            (PCI pertains solely to cardholder data (CHD), the authorization/capture token holds
            no value and is therefore beyond the scope of PCI compliance). This is used in
            refunds; it will also be passed down to OMS / TLog.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">What are unreferenced vs no receipt returns?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">
            <p>Unreferenced are returns to any credit card that the customer provides. Typically
              used when payment gateway is migrated or migrating to a new OS or for legacy
              orders.</p>
            <p style="margin-bottom:0;">No receipt returns are used when the customer returns an item without a receipt.
              The customer can get payments through any tender that is configured in the return
              policy.</p>
          </td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">What about taxes and promotions for no receipt returns?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">This can be configured to return taxes / promotional prices for non-receipt
            returns.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">What GiftCards are supported?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Givex, Clutch</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">How is integration done with Givex?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">For Givex, we are using JSON-RPC spec on their DataConnect protocol.</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">How are multi-tender returns managed?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">By default, multi-tender returns follow the First In, First Out (FIFO) principle.
            This means that the tender that was initially used will be the first to be refunded.
            For example, if a gift card was the first tender used for the transaction, the return
            will also be processed back to the gift card first. However, if the amount on the
            original tender (e.g., gift card) is insufficient to cover the complete amount, the
            associate will have the additional option to process the refund on the next tender
            used (e.g., credit card). </td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">Can we support cross-region returns?</td>

          <td class="slds-cell-wrap" style="vertical-align:top;">No, this is not supported by POS or OMS. </td>

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