Payment Gateway Integrations

Payment Gateway Integrations

Payment Gateway Integrations

"Setting up the payment options for customer checkout"

The Payment Gateway integration lets you accept online payments from customers in your FTx Commerce store. 
  1. FTx Commerce supports three payment gateways: Datacap | USAePay | NorthPay. You must have an activated payment gateway merchant account. You can choose one gateway at the global level, and it applies automatically to all your store locations. To configure the payment integration, retailers must have a developer account with their preferred payment gateway and obtain the required integration credentials and payment configuration from the respective provider.
  2. FTx Commerce also supports North Embedded Checkout to offer Google Pay™ and Apple Pay as payment options on the FTx Commerce Online Store checkout.
  3. You can also manage the Payment Service logos, which are the card and payment brand icons displayed in the “We accept” section of your online store’s footer and in the main sidebar menu of your mobile app (PWA), accessed through the hamburger menu. They tell customers which payment methods are acceptable.

1. Reaching "Payment Gateway"

As a retailer/store admin, you can integrate any Payment Gateway to receive the payment for online orders through the FTx Commerce store.
Follow the steps below to integrate any payment gateway:
  1. Step 1: Log into Store Admin
  2. Step 2: Click Integrations -> Payment Gateway

Figure 1.1 - "Payment Gateway"
NotesNote: To configure the integration, retailers must have a developer account with their preferred payment gateway and obtain the required integration credentials and payment configuration from the respective provider. 

2. Payment Gateway Integrations

2.1 Global-Level Payment Gateway

1. Prerequisites
FTx Commerce - Payment Gateway
Before configuring any payment gateway, ensure that:
  1. You have an active developer account for which you want to enable.
  2. You have the required integration credentials, such as authorization details, API keys, client keys, or other provider-specific configuration values.
  3. The required payment options are configured and enabled through the payment gateway provider's account.
Notes
Note: The API credentials and configuration fields required may vary depending on the payment gateway selected by the retailer for integration with the FTx Commerce Online Store.
FTx Commerce - Control Center
  1. The retailer must configure a tender under "Store Admin → Assign Tenders" and map it to the corresponding "POS Tender" in Control Center for Credit/Debit Card transactions.
  2. This tender mapping is mandatory for sales posting to ensure accurate payment method identification and reporting in CC.
2. Select a Payment Gateway

Choose one of the available payment gateway providers: DataCap | USAePay | North Pay.


Figure 2.1.1 - Choose Payment Gateway

3. Enter Integration Credentials

Enter the credentials & configuration details provided by the selected payment gateway. The required fields may vary depending on the provider.

NotesNote: FTx Commerce does not generate the payment credentials. The retailer must get the credential values from your payment provider and paste them here to establish the connections. 

Figure 2.1.2 - Enter Credentials

4. Complete the Integration

Save the configuration payment integration according to the provider's supported environment.

Notes
Restriction when changing the payment gateway:
You cannot change the payment gateway while orders are in progress with the current payment method. Wait until those orders are completed, then switch gateways.

2.2 Location-Level Payment Gateway

Each location can either use the global configuration or have its own credentials. Choose one of the following:
  1. Use Business Level Payment Config: The location uses the default gateway and credentials set at the global level.
  2. Use Location Payment Config: The location uses the same payment gateway with different API credentials.

Figure 2.2.1 Location-Level Payment Gateway

Location-Level Payment Gateway Rules:
  1. A location cannot use a different payment gateway from the one selected at the global level.
  2. A location can use the same gateway with different credentials. For example, if North Pay is the global gateway, a location can use its own North Pay with different credentials.

2.3 Tracking Payment Transactions

When an order payment-related query arises in FTx Commerce, the retailer's team should review the transaction in the payment gateway's reporting or transaction management portal and compare it with the order and payment records available in FTx Commerce and Control Center -> E-Journal.

This is particularly useful for investigating:
  1. Successful, declined, or pending transactions.
  2. Refund status and refund amounts.
  3. Differences between the order total and the amount charged.
  4. Payment processing fees and other applicable charges.
  5. Duplicate charges, failed payments, and transaction reconciliation discrepancies.
1. DataCap
  1. Open Credit Transactions → Credit Transactions to review transaction details.
  2. Use filters such as invoice, amount, batch, reference number, or account/MID to locate a transaction.
  3. Open Gateway → Batches to review batch-level transaction activity, where supported.
  4. For refunds and fee verification, review the available transaction records and applicable merchant processing statements.
2. USAePay
  1. Open Transactions to investigate individual payment transactions and refunds.
  2. Open Batches → Batch Manager to review sales, voids, credits/refunds, and batch totals.
  3. Open Reports → Transaction Overview / Transaction List for transaction-level reporting.
  4. For processing fees, check the merchant service provider's statements, as gateway transaction records do not necessarily show all processing costs.
3. North Pay
  1. Review transaction and deposit activity through the available reporting dashboard.
  2. Use daily summaries, custom reports, and downloadable CSV reports to investigate sales, refunds, voids, and deposits.
  3. Review the applicable merchant processing statements to verify processing fees and other charges. 
NotesNote: The exact navigation and available reports depend on the retailer's payment gateway account, permissions, and provider configuration.

3. Embedded Checkout [Google/Apple Pay]

North Embedded Checkout enables retailers to offer Google Pay™ and Apple Pay as payment options on the FTx Commerce Online Store checkout. Customers can select an available wallet at checkout and authorize payment using an eligible payment method saved in their Google Pay or Apple Pay wallet.
1. Prerequisites
FTx Commerce - North Embedded Checkout
  1. The retailer must have an active North Pay developer account with access to Embedded Checkout.
  2. The retailer must have the required permissions to configure checkout and payment methods.
  3. The retailer must identify the storefront domain where checkout will be displayed.
  4. The retailer has to obtain the credential from North Checkout Designer.
NotesNote: Apple Pay requires domain verification and registration for the storefront domain when using Embedded Checkout. Google Pay does not require separate domain registration for this North-hosted integration.
FTx Commerce - Control Center
  1. The retailer must configure a tender under "Store Admin → Assign Tenders" and map it to the corresponding "POS Tender" in Control Center for Google Pay / Apple Pay transactions.
  2. This tender mapping is mandatory for sales posting to ensure accurate payment method identification and reporting in CC.
2. North Checkout Design and API Credentials
  1. Configure Checkout: Log into the North Developer Portal, open Embedded Checkout, and create or configure the checkout profile.
  2. Enable Wallets: Configure Google Pay and Apple Pay as supported payment options.
  3. Register Domain: Complete Apple Pay domain verification and registration.
  4. Obtain Credentials: Collect the required Private API Key, Checkout ID, and Profile ID from the North checkout configuration.

Figure 3.1 - North - Embedded Checkout Info

3. Integration in FTx Commerce Store Admin
Once the North checkout has been configured and the required credentials are available, complete the integration in Store Admin.

Navigate to the payment gateway configuration section.

  1. Step 1: Log into Store Admin
  2. Step 2: Click Integrations -> Payment Gateway
  3. Step 3: Click Embedded Checkout

Figure 3.3 - Embedded Checkout -> Configure Fields

Enable the "Embedded Checkout..." option and enter the required credentials and identifiers obtained from the North Developer Portal:

  1. Private API Key (Checkout): Authenticates server-side requests to North.
  2. Checkout ID: Identifies the configured Embedded Checkout instance.
  3. Profile ID: Identifies the merchant profile associated with the checkout.
  4. Test Credentials: Perform the necessary testing to confirm that the integration works as expected.
Note: Before enabling the options for customers, ensure that:
  1. The North checkout design configuration has been saved.
  2. Apple Pay domain registration is complete.
  3. Google Pay and Apple Pay are enabled in the North checkout configuration.
  4. Enter the values exactly as provided by North.

4. Assign Tenders for Payment Options

Tender Assignment in FTx Commerce Store Admin maps each payment method and options to the corresponding POS Tender configured in Control Center. This mapping ensures that when FTx Commerce orders are posted as sales in CC, the payment method is aligned with the appropriate tender and its configured reconciliation bucket.

Step 1: Ensure POS Tenders Are Configured in Control Center
  1. Navigate to POS → Maintenance → Tenders in CC to create/manage the Tenders.
  2. Assign the appropriate "Reconciliation Bucket" for the tender based on the payment method and financial reconciliation requirements.

Figure 4.1
 - CC- > Tender

Step 2: Assign POS Tender in Store Admin
  1. Navigate to Store Admin → General → Settings → Assign Tenders.
  2. For each applicable payment method, select the corresponding POS Tender configured in CC.
  3. Ensure the mapping is correct for all supported payment methods and options, such as Credit/Debit Cards, Google Pay/Apple Pay, Gift Cards, and other applicable tenders.

Figure 4.2 - Store Admin -> Tender Assignment

5. Payment Service Logos

This section allows retailers to manage the payment service logos displayed in the “We Accept” section in the FTx Commerce storefront footer menu and main sidebar menu in the mobile app (PWA).

Figure 5.1 - Manage Payment Logos

Configuration Steps:
  1. Navigate to Store Admin → Payment Gateways → Payment Services Logos.
  2. Enable or disable the logos for supported payment services, such as Visa, Mastercard, Maestro, Discover, Cirrus, and American Express.
  3. Click "Save" to apply the changes.
NotesNote: Enabling or disabling a payment service logo only affects its visibility on the storefront footer menu and main sidebar menu in the mobile app (PWA). It does not enable, disable, or impact the functionality of the corresponding payment service. Payments will continue to be processed according to the configured payment gateway and supported payment methods.

6. Customer Checkout Payment Options

During checkout, customers can select one of the available payment options configured by the retailer through Store Admin.

Figure 6.1 - Payment Options

Available Payment Options:
  1. Customer can select:
    1. Credit/Debit Card: Payments processed through the configured gateway—DataCap, USAePay, or North Pay, OR
    2. Google Pay / Apple Pay: Wallet payments processed through North Embedded Checkout, when enabled.
  2. Additional Payment Benefits: Customers can apply available LNS/Discount Coupons, Loyalty Dollars, and Gift Cards toward their order, subject to applicable eligibility and configuration rules.
  3. Order Placement: Customers select their preferred payment option, apply any eligible discounts or balances, acknowledge the payment authorization, and click Place Order to complete checkout.