The Fortis app utilizes the Check offline payment method as a framework for the payments app. Below are the steps to enable it in your store:
Select Settings in the store menu.
Select ‘Offline Payment Methods,’ select ‘Check’ from the drop-down menu and click ‘Set Up.’
Set up the ‘Check’ payment method and give it the name 'Fortis.' NOTE: The name of the payment method is used in the configuration process, and it must be correct for the app configuration to be completed successfully.
Set up the ‘Check’ payment method and give it the name Fortis. NOTE: The payment method name is used in the configuration process and must be correct for the app configuration to be completed successfully.
Step 2 – Set Up Store Level API Accounts
Select Settings from the store menu.
Navigate to the ‘API’ section of the Settings page, and select ‘Store-level API Accounts.’
Click the ‘Create API Account’ button to create a new API account.
Create the API account with the following settings:
Token type: V2/V3 API Token
Name: Fortis
OAuth Scopes:
Carts: Modify
Checkouts: Modify
Checkout Content: Modify
Store Locations: Read Only
Create Payments: Create
Get Payment Methods: Read Only
Sites & Routes: Read Only
Storefront API Tokens: Manage
Content: Modify
Customers: Read Only
Information & Settings: Modify
Orders: Modify
Order Transactions: Modify
Click Save
When you click Save, a pop-up with the BigCommerce API Credentials will appear. NOTE: Please copy the Client ID, Client Secret, and Access Token credentials. If you are using Chrome, Firefox, or Edge, a file with the credentials will also be downloaded.
Step 3 – Install the App
Click to install the Fortis app on your store.
Select the Apps menu option and click on the App to open the configuration page.
2. App Configuration
Once you have installed the Fortis app, you must input the BigCommerce and Fortis API keys on the configuration page to complete the setup. The configuration page is divided into sections based on functionality.
2.1 Store-level API settings
Enter the store-level API credentials created in Step 2 of the store setup process. The values will be masked after you have entered them.
2.2 Gateway Settings
Fortis gateway API keys are required for the app to connect to the Fortis gateway and run transactions. The gateway validates the API keys. If incorrect credentials for the environment or account are used, the gateway will not be able to authenticate the connection and will return an error message.
2.2.1 Store Settings
The credentials entered in the Store settings section can be found in your Fortis gateway merchant portal. If you have both a sandbox account and a live account with Fortis, each account will have a unique set of API keys.
The payment settings enable payment methods and payment processing actions on the app.
Action – This sets the mode of processing for credit card transactions:
Sale – A credit card transaction is authorized and captured in one transaction
AuthOnly - A credit card transaction is authorized and must be captured to receive the payment. The capture can be done via the Fortis gateway portal or in an external system such as ERP software. NOTE: ACH is not supported as a payment method for the AuthOnly action
Enable Google Pay and Enable Apple Pay
Tick the appropriate tick boxes to enable Google Pay and Apple Pay as payment methods on the app. Please note that these are not enabled by default on your gateway account and must be enabled on the gateway to offer them as payment methods.
Enable ACH and CC Transactions
Tick the appropriate tick boxes to enable Credit Card and ACH as payment methods on the app. Please ensure that the payment method you are enabling is active on your gateway account.
Vault
Tick this box to enable customers who create accounts on your store to save a payment method and use it to make future payments. A customer can store and use multiple payment methods. Please ensure that tokenization is enabled on your gateway account before enabling Vault on your store.
2.2.3 Appearance Settings
The Appearance Settings set the styling and color scheme for the payments app. Fonts, line spacing, and colors can be customized.
2.2.4 Testing the App
The app supports both a test (sandbox) mode and a live mode. In test mode, transactions are run in the Fortis sandbox environment. This environment is used to test the payment responses and functionality without creating an actual charge. We highly recommend testing in the sandbox environment on a staging site before deploying to production.
To request a test account, please sign up on our Developer Portal here: Dev Portal
Please include 'BigCommerce' in the Referred By field.
3. Refund
A payment received via the Fortis app can be refunded either directly on the Fortis gateway portal or by external ERP software. Transactions cannot be refunded directly within the store’s admin dashboard.
When a partial or full refund is created for a transaction, the Fortis app updates the BigCommerce order status to Refunded for a full refund or Partially Refunded for a partial refund.
NOTE: This update is to the order status only and may require intervention to return order items to stock in the Big Commerce store.
4. Void
A payment received via the Fortis app can be voided either directly on the Fortis gateway portal or by external ERP software. Transactions cannot be voided directly within the store’s admin dashboard.
A pre-authorized transaction can be voided at any time before it has been captured. A Sale transaction and a captured authorized transaction are part of a settlement batch and can only be voided before the settlement batch is closed.
When a transaction is voided, the Fortis app updates the BigCommerce order status to Cancelled. NOTE: This update affects the order status only and may require intervention to return order items to stock in the Big Commerce store.
5. Capture
If you have set the Fortis app’s Action to ‘Authorize only,’ credit card payments made on your site will be pre-authorized but will require the transaction to be captured for you to receive the funds.
NOTE: Authorized transactions must be captured or voided within the authorization window recommended by the card brands to avoid penalties and downgrades for late settlement.
Authorization can be captured manually using the Fortis gateway portal or by importing the transaction data into an ERP system and creating the capture within the software.
When the payment is successfully authorized, the BigCommerce order will have the status of Awaiting Payment. Once the authorization is captured, this order status will change to Awaiting Fulfillment.
6. ACH Settlement Process
ACH transactions have a 'Pending' status when they are created and move through a settlement process. The gateway transaction status changes as the transaction moves through the settlement process.
The ACH statuses and gateway status codes are shown below:
An order paid using ACH will have an initial status of Pending. This status will change to Awaiting Fulfillment when the ACH transaction status changes to Settled (134).
