- The retailer must have an active North Pay developer account with access to Embedded Checkout.
- The retailer must have the required permissions to configure checkout and payment methods.
- The retailer must identify the storefront domain where checkout will be displayed.
- The retailer has to obtain the credential from North Checkout Designer.
Note: 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
- 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.
- 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
- Configure Checkout: Log into the North Developer Portal, open Embedded Checkout, and create or configure the checkout profile.
- Enable Wallets: Configure Google Pay and Apple Pay as supported payment options.
- Register Domain: Complete Apple Pay domain verification and registration.
- 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.
- Step 1: Log into Store Admin
- Step 2: Click Integrations -> Payment Gateway
- 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:
- Private API Key (Checkout): Authenticates server-side requests to North.
- Checkout ID: Identifies the configured Embedded Checkout instance.
- Profile ID: Identifies the merchant profile associated with the checkout.
- Test Credentials: Perform the necessary testing to confirm that the integration works as expected.
Note: Before enabling the options for customers, ensure that:
- The North checkout design configuration has been saved.
- Apple Pay domain registration is complete.
- Google Pay and Apple Pay are enabled in the North checkout configuration.
- 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
- Navigate to POS → Maintenance → Tenders in CC to create/manage the Tenders.
- 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
- Navigate to Store Admin → General → Settings → Assign Tenders.
- For each applicable payment method, select the corresponding POS Tender configured in CC.
- 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