Bigcommerce
Features
The BigCommerce app offers the following features, which can be customised as required:
Detailed feature description:
- Simple and fast configuration;
- Wide availability of alternative payments;
- Order and invoice management via server-to-server calls (orders, refunds, pre-authorizations);
- Fast payment management via the form rendered on the BigCommerce checkout page.
Merchant back-office configuration
In the merchant back-office provided, you can retrieve credentials, SHOP Login and API Key, to be reused when configuring the application in the BigCommerce back-office.
Within Configuration > Security > APIKEY you can create the required value
By pressing the Add Key button
Then press the copy button, highlighted in the figure, to copy the key to clipboard, for later use on the BigCommerce backend
Within Payment Page > Fields & Parameters the PaymentMethod parameter must be enabled in the response, on both pages
By checking the two entries visible in the following screen
Application installation information
To proceed with the application installation, you need to access the BigCommerce Developer Portal via the link available in the back-office under the "Develop" section of the "App" menu.
Once logged into the Developer Portal, go to the "Overview" section of the "Apps" menu and then select the "Create App" button.
After selecting the "Create App" button, enter "Ecommerce Sella" as the application name and click "Generate Credentials" to obtain the credential pair needed for the application configuration.
The credential pair needed for the configuration is shown in a notice displayed immediately after the action, in the "Client ID" and "Client Secret" fields. These credentials can also be retrieved at a later time.
Next, by accessing the App detail, clicking on the application name "Ecommerce Sella" in the list on the "Overview" page of the "Apps" menu, you need to configure the "Callback URLs" section within the already displayed "App information" tab. Follow this logic to fill in the three fields:
- Auth: https://bigcommerce-sella.iplus.it/bigcommerce/auth
- Load: https://bigcommerce-sella.iplus.it/bigcommerce/load
- Uninstall: https://bigcommerce-sella.iplus.it/bigcommerce/unistall
In the section below, "App users", disable the toggle with the label "Enable multiple users".
Next, configure the application scopes by accessing the "Scopes" tab, selecting the corresponding entry at the top of the page.
Refer to the following table to set all the entries on the page.
| SCOPE | PERMISSION |
|---|---|
| Orders | Modify |
| Order Transactions | Read-Only |
| Fulfillment Methods | None |
| Order Fulfillment | Modify |
| Create Payments | Create |
| Get Payment Methods | Get |
| Stored Payment Instruments | Read-Only |
| Products | None |
| Store Inventory | None |
| Store Locations | None |
| Customers | Read-Only |
| Customer Login | None |
| Content | Modify |
| Checkout Content | Modify |
| Marketing | None |
| Themes | None |
| Carts | Read-Only |
| Checkouts | Read-Only |
| Channel Settings | Read-Only |
| Channel Listings | Read-Only |
| Information and Settings | Read-Only |
| System Logs | None |
| Sites and Routes | Read-Only |
| Storefront API Tokens | None |
| Storefront API Customer Impersonation Tokens | None |
| App Extensions | Manage |
| B2B Edition | None |
Finally, by accessing the "Listing information" tab at the top of the page, configure the "Storefront type" entry by setting it to "Multi Storefront".
Within this section, you can add the logos displayed in the back-office to identify the newly created and configured application, using the "App icon" and "Primary logo" fields.
Application configuration
After installing the application, you need to configure the options made available through the BigCommerce back-office.
In the dedicated "App" section there is the "Ecommerce Sella" block for application configuration.
You can configure:
- module activation: enables the display of payment methods provided by Sella during checkout;
- test mode activation: allows you to use the payment gateway sandbox with the corresponding test ShopLogin and API Key;
- Wallet & Click2Pay activation: enables access to Apple Pay, Google Pay and Credit Card services on the new Fabrick Payment Orchestra page;
- credit card and PayPal operation type selection: identifies the settlement method: if set to "Authorization and capture" the transaction, if authorized, is also captured automatically; if set to "Authorization" the transaction, if authorized, requires a manual operation to be captured unless the terminal has been configured with M.O.T.O. Unify transaction.
Here is an example of the configuration section:
Additionally, with Fabrick Payment Orchestra, you can configure the visibility of individual payment methods. If needed, a dedicated button is provided to hide a method.
Payment method configuration
There are two fields for managing extra configurations on specific payment methods:
- Consel, where, upon enabling the method, you need to specify the Merchant Promotional Code;
- PayPal, for which you can choose the operation type: authorization and capture or authorization.
There are also two specific fields for entering the Shop Login and API Key credentials.
When saving the configuration, the entered credentials are validated. If valid, the application will synchronize all active payment methods on the terminal to offer them during checkout to the end customer.
If payment methods are updated in the merchant back-office, a cron job periodically synchronizes the list.
If the merchant wants to synchronize payment methods with immediate effect, they will need to save the application configuration on BigCommerce again.
Card payment flow
The card payment process provides two operating modes:
- Through the payment form integrated directly in the BigCommerce checkout;
- Through the external payment page provided by Fabrick Payment Orchestra, by enabling the "Wallet & Click2Pay" option in the application configuration.
In the first scenario, the user, after browsing the e-commerce site, accesses the checkout page and sees the form for entering their payment card details.
At the end of the payment, in case of a positive outcome, the user will be redirected to the confirmation page and will receive an email containing the transaction details.
In case of a negative outcome, the user will be redirected to the previous checkout page, with the cart already populated and an explanatory message.
In the second scenario, the user, after browsing the e-commerce site, accesses the checkout page and sees the "Payment cards, Wallet & Click2Pay" option.
By selecting this method, the payer will be redirected to the Fabrick Payment Orchestra payment page, where they can choose to complete the transaction via payment card or through one of the available wallets (Google Pay, Apple Pay).
At the end of the payment, in case of a positive outcome, the user will be redirected to the confirmation page analyzed above (identical to scenario 1) and will receive an email containing the transaction details.
Similarly, in case of a negative outcome, the user will be redirected to the previous checkout page, with the cart already populated and an explanatory message.
Order and transaction management information
Authorization request
With the M.O.T.O. configuration, Fabrick allows separating the authorization and capture phases. If activated, the first transaction is limited to the authorization request, otherwise Fabrick captures the amount immediately after authorization.
The application works according to the chosen configuration described in the Application configuration section.
In the dedicated section (Orders > All orders) all orders placed through the e-commerce are listed. By clicking the icon at the end of each table row, you can access the "Ecommerce Sella -- Payment detail" section, where transaction details and the list of associated movements are available.
Capture
With the capture operation, the authorized total is permanently transferred to the merchant's bank account. To use this operation, the M.O.T.O. function must be configured so that it is separated from the authorization.
With this configuration, BigCommerce creates a new order and during payment the amount is held through the authorization operation (the merchant receives an email from Fabrick). When the invoice is requested, BigCommerce requests Fabrick to capture the authorized amount, which proceeds and sends an email to the merchant.
The operation can be performed through the BigCommerce back-office, by clicking the icon at the end of each table row and selecting "Ecommerce Sella -- Payment detail" as illustrated in the previous section.
Within the detail tab, there is a dedicated option to capture or cancel an authorization.
Cancellation
Cancellation can be requested for an authorized but not yet captured transaction, and the M.O.T.O. function must be set with the separation of authorization and capture. The operation can be performed using the dedicated form illustrated in the previous section by clicking the dedicated button without specifying any amount.
Refund
Refunds can only be requested on already captured payments. From a fiscal standpoint, the operation involves a charge to the merchant and a credit to the customer's card.
A transaction can be refunded totally or partially multiple times, up to the total payment amount. The operation can be performed using the dedicated form illustrated in the previous section by entering the desired amount and clicking the dedicated button.
CRON Job
Using the CRON Job, the Ecommerce Sella application can:
- handle the Waiting(XX) status returned by certain payment methods that do not immediately return an OK or KO upon order confirmation;
- update the available and visible payment methods configured for the terminal.