Skip to main content

Salesforce CC

Use the guides below to enable the Splitit installments payment option in the payment and checkout experience on your Salesforce site, along with messaging that will introduce your customers to installment payment options early in their shopping experience.

SiteGenesis

Overview

The Splitit payment cartridge enables a CC store to integrate with the Splitit payment service. This document provides detailed instructions on installing a Splitit payment cartridge into a CC store.

The integration is based on the SiteGenesis demo store, provided by SFCC.

The integration consists of an archive with contents as described in the below table.

NamePurpose
cartridgesContains Splitit integration cartridges
cartridges\int_splitit_sgThis cartridge contains the SiteGenesis specific changes required for Splitit integration
cartridges\int_splititThis cartridge contains the API calls for Splitit integration and common code extensions
cartridges\splitit_sg_changesThis cartridge references all the changes done to OOB SiteGenesis files. Please do not include this in the cartridge path and this is for reference purposes only
cartridges\bm_splititThis cartridge contains Business Manager UI, BM-related system extensions to add/update general, API, payment, and upstream messaging configurations
cartridges\bm_splitit_demoThis cartridge contains BM-related system extensions to testing and validating payment flows (cancel, refund, and capture of charges)
metadataContains custom objects and settings required for the integration
documentationContains this document “Splitit SiteGenesis Integration Document”

Features

The integration described in this document supports the following features:

  • Embedded card form checkout using Splitit Flex Fields payment
  • Hosted page checkout using Splitit Hosted payment.
  • Installment banners that have been implemented using Splitit Upstream Messaging
  • Ability to enable/disable the payment methods based on currency and country.
  • Ability to configure Splitit settings via a customer-friendly UI interface.

Splitit Flex Fields Payment

Splitit's Flex Fields is a unique product that allows you to fully integrate Splitit into the checkout process on your website, both stylistically and functionally. Flex Fields are individual iFrames plugged directly into the Splitit servers, however, you can extensively customize them. For this customization, we have implemented an intermediate page for the checkout process.

Splitit Hosted Payment

Splitit's Hosted Payment features a full redirect from the merchant site to Splitit's. To use it, fetch a URL from the Splitit API then send your customer there to enter credit card data. After the customer is done checking out, based on the outcome of the transaction, the customer is redirected to the appropriate endpoint within SFCC (success, cancel, or failure).

Splitit Upstream Messaging

Splitit's Upstream Messaging informs the customer early on in their journey on your website that Splitit will be available at checkout. It uses banners, price breakdowns, and Splitit messages that can be added to your home page, footer, product page, cart page, and checkout pages.

Payment Types Supported

Credit cards supported currently

  • Visa
  • Mastercard

Limitations, Constraints

Please check with Splitit to find out which languages are currently supported.

Compatibility

Available since Commerce Cloud Platform Release 21.2, Site Genesis 105.1.1.

Installation

Cartridges

Upload the following cartridge to the BM code version

  • int_splitit_sg
  • int_splitit
  • bm_splitit
  • bm_splitit_demo (Ony on developer sandboxes)

Configure the cartridge path as shown in the below tables. Cartridges should be added to the beginning of the cartridge path.

Site Cartridge Pathint_splitit_sg:int_splitit
BM Cartridge Pathint_splitit:bm_splitit:bm_splitit_demo

Metadata

All BM configurations related to the below components have been configured within metadata/site-template folder.

  • System/Custom object definitions
  • Payment Methods
  • Payment Processors
  • Services
  • Jobs
  • Content

Please follow the below steps to import the BM configurations for the above-mentioned components

  1. Locate the folder metadata in the installation package.
  2. Review the contents within site-template folder.
  3. Change the site ID under path site-template\sites to your site ID.
  4. Change the library ID under path site-template\libraries to your library ID
  5. Archive the folder to ‘site-template.zip’ and then Import the file via Site Import & Export
Services

Two new services, “splitit.http.sandbox” and “splitit.http.production”, has been created as part of the integration.

Service IDService ProfileService Credential
splitit.http.sandboxsplitit.http.sandbox.profilesplitit.http.sandbox.credentials
splitit.http.productionsplitit.http.production.profilesplitit.http.production.credentials

The URLs for the sandbox and production endpoints have been configured within the cartridge.

EnvironmentURL
Non-production instanceshttps://webapi.sandbox.splitit.com/api
Production instanceshttps://webapi.splitit.com/api
Payment Processor

Two new payment processors have been created as part of the cartridge.

  • SPLITIT_FLEXFIELDS
  • SPLITIT_HOSTED
Payment Processor IDPurpose
SPLITIT_FLEXFIELDSPayment processor for processing transactions using the FlexFields (embedded card form) integration
SPLITIT_ HOSTEDPayment processor for processing transactions using the Hosted page (external redirection) integration
Payment Methods

A new payment method, Splitit has been created as part of the cartridge.

Jobs

A new job SplititWebhookNotifications has been created as part of the cartridge and is available under Administration > Operations > Jobs. This job processes the CreateSucceeded webhook notifications received from Splitit and processes them in recurring intervals.

Please follow the below steps to configure the job:

  1. Navigate to Administration > Operations > Jobs > SplititWebhookNotifications
  2. Select the Schedule and History tab.
  3. Check the Enabled checkbox.
  4. Set the Trigger as Recurring Interval
  5. Configure the start date and recurring interval duration. It is recommended that the recurring interval is >= 5 minutes.

The below image is for reference purpose only.

webhook notifications
  1. Click on the Job Steps tab.
  2. Click on Scope and select the relevant sites
select scope
Content

The following content assets have been created as part of the cartridge

  • splitit_homepage_banner
  • splitit_footer_banner
  • splitit_hostedpayment_paymenttab_message

The following content slots have been created as part of the cartridge

  • splitit-home-page-banner

Custom BM Module

A custom BM module has been developed to allow merchants to be able to configure all the Splitit related configurations in one place. This module has been developed using custom objects and not site preferences due to limitations around data replication and API availability for updating site preferences.

IMPORTANT: The custom objects are non-replicable. Hence please complete Splitit production configurations directly on the SFCC Production Instance itself. Configurations through this module cannot be replicated via data replication.

Please follow the below steps to provide permissions to view this BM module.

  1. Navigate to Administration > Organization > Roles & Permissions.
  2. Select the role that you would want to give access to the BM module.
  3. Select the Business Manager Modules tab.
  4. Select all the relevant sites where Splitit would be configured.
select sites
  1. Select the following modules from the popup and apply the changes
select modules
  1. Confirm that the following section is visible in the Merchant Tools overlay
merchant tools overlay section

Configurations

The below sections explain how to set up the Splitit integration-related configurations within Business Manager.

Payment Methods

Please refer to the below table while configuring the Splitit payment method.

Payment Method SettingValueDescription
Payment ProcessorSPLITIT_FLEXFIELDS OR SPLITIT_HOSTEDPlease select the relevant Payment Processor based on your mode of integration – FlexFields or Hosted
Min/Max Payment RangesDo not configureDo not configure the min/max payment ranges for currencies. This will be handled via a separate set of configurations.
CurrenciesBased on requirementsPlease configure the applicable currencies based on your requirements.
CountriesBased on requirementsPlease configure the applicable countries based on your requirements.

IMPORTANT: When any of the Payment Method settings have been modified, ensure that the Splitit custom cache is always cleared. Please refer to this link for more details regarding custom cache – Splitit Custom Cache.

Splitit General Configurations

The General Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Enable Splitit On/OffControls whether the Splitit integration is enabled for the site
API failure email recipientsConfigure email addresses where notifications regarding email failure should be sent to.
general configurations

Splitit API Configurations

The API Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
API UsernameThis configuration is used within the Login API call which generates the Splitit session id. The value for this configuration can be retrieved from Splitit Dashboard > Credentials > Splitit Integration Credentials > API User Name
API PasswordThis configuration is used within the Login API call which generates the Splitit session id. The value for this configuration can be retrieved from Splitit Dashboard > Credentials > Splitit Integration Credentials > API User Password
API KeyThis configuration is set within the header of all the Splitit API calls (except Login). The value for this configuration can be retrieved from Splitit Dashboard > Credentials > Gateway Provider Credentials > Payment Terminal API Key
Splitit EnvironmentConfigure the Splitit environment this integration would use. On Production SFCC instances, this must be set to Production. On non-production SFCC instances, this must be set to Sandbox

The Check Credentials button when clicked validates the following

  • Format of API Key (does not check if the API key value is valid)
  • API User Name and API Password against the Splitit Environment selected
api configurations

Splitit Payment Configurations

The Payment Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Enable 3DSThis configuration is used to enable/disable 3DS validation while processing payments.
Payment ActionThis configuration indicates whether the first installment must be captured on order placement or once the order is dispatched.
payment configurations

Splitit Upstream Messaging Configurations

The Upstream Messaging Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Minimum amount to display the Splitit installment price on PDPThis configuration determines what is the minimum product price required to display the Upstream messaging banners on PDP. Currency-specific amounts can be set. All currencies enabled for the site will be listed here.
Upstream messaging selectionThis is a multi-select configuration with which merchants can decide which pages should display the Upstream Messaging Banner.
Footer allowed card brandsThis is a multi-select configuration that indicates which of the card brand logos must be displayed within the Footer upstream messaging banner. The values selected here would also be used to render the card logos shown against the Splitit payment method tab on the checkout page.
messaging configurations

Splitit Installment Configurations

The Installment Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Installment Configurations Min/Max currencyThis is a currency dropdown that lists all the currencies enabled on the site. Merchants can configure currency-specific installment ranges and the applicable number of installments by selecting the currency from this dropdown.
Amount FromIndicates the lower limit of the order total range.
Amount ToIndicates the upper limit of the order total range
No. of installmentsComma-separated list of installment options to be presented to the customer on the checkout page for the particular range

Steps to be followed while configuring installment range and options:

  1. Pre-determine the different order total ranges and the number of installments to be presented to the customers on the checkout page.
  2. Select the currency from the currency dropdown.
  3. Using the Add button creates an entry for the range.
  4. Enter the lower amount of the order total range within the Amount From column
  5. Enter the upper amount of the order total range within the Amount To column
  6. Enter the number of installments to be presented to the customers for this particular order total range.
  7. Repeat steps 4 – 6 if more than one range is applicable as per business requirements.
  8. Click on Save
  9. Repeat steps 1 – 8 for other currencies (if applicable)
installment configurations

Storefront Cartridge Changes

For the Splitit integration to work on SiteGenesis, a few changes are required to be made on the SiteGenesis storefront cartridges.

Controller Changes

COPlaceOrder.js

File location: "sitegenesis storefront controller cartridge}\cartridge\controllers\COPlaceOrderjs"

Global Changes

Add the following lines of code in orange at the class level:

select modules

The changes should reflect as shown below.

two functions

Function - handlePayments()

Add the following lines of code in orange to the function handlePayments as shown below:

function handlePayments function handlePayments part two

The changes should reflect as shown below:

function handlePayments changes

Function (NEW) – handleSplititRedirect()

Add this new function to the controller:

function handlePayments changes

Function - start() Add the following lines of code in orange to the function start() as shown below:

function start function start two

The changes should reflect as shown below:

function start changes
COBilling.js

File location: sitegenesis-storefront-controller-cartridge\cartridge\controllers\COBilling.js

Function (NEW) – handleSplititPayments()

Add this new function to the controller:

function handleSplititPayments

Function - returnToForm()

Add the following lines of code in orange to the function returnToForm() as shown below:

function returnToForm

The changes should reflect as shown below:

function returnToForm changes

Function - publicStart()

Add the following lines of code in orange to the function publicStart() as shown below:

function publicStart

The changes should reflect as shown below:

function publicStart changes

Client-Side JS Changes

Billing.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/pages/checkout/billing.js

Function - updatePaymentMethod()

Add the following lines of code in orange to the function updatePaymentMethod() as shown below:

function updatepaymentmethod

The changes should reflect as shown below:

function updatepaymentmethod changes

Function - init()

Add the following lines of code in orange to the function init() as shown below:

function init

The changes should reflect as shown below:

function init changes
Index.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/pages/checkout/ index.js

Global Changes

Add the following lines of code in orange at class level:

global changes

Function – init()

Add the following lines of code in orange before the end of function init() as shown below

function init

The changes should reflect as shown below:

function init changes
Shipping.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/pages/checkout/shipping.js

Global Changes

Add the following lines of code in orange at class level:

global changes global changes two

Function – updateSummary()

Add the following lines of code in orange to the function updateSummary() as shown below:

function updateSummary

The changes should reflect as shown below:

function updateSummary changes
Index.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/pages/product/index.js

Global Changes

Add the following lines of code in orange at class level:

global changes

Function – initializeEvents()

Add the following lines of code in orange to the function initializeEvents() as shown below:

function initializeEvents

The changes should reflect as shown below:

function initializeEvents changes
ProductSet.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/pages/product/productSet.js

Add the following lines of code in orange at class level:

messaging

Function – module.exports

Add the following lines of code in orange to the function module.exports as shown below:

function module.exports

The changes should reflect as shown below:

function module.exports changes
Variant.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/pages/product/variant.js

Add the following lines of code in orange at class level:

function module.exports changes

Function – updateContent()

Add the following lines of code in orange to the function updateContent() as shown below:

function update content

The changes should reflect as shown below:

function update content changes
Quickview.js

File location: sitegenesis-storefront-core-cartridge/cartridge/js/quickview.js

Add the following lines of code in orange at class level:

upstream include

Function – quickView.setup()

Add the following lines of code in orange before the end of function quickView.setup() as shown below:

quickview setup function

Function – show()

Add the following lines of code in orange to the function show() as shown below:

function show

The changes should reflect as shown below:

function show changes

Custom Files

SplititCheckout.js

This is a new file that needs to be copied into the SiteGenesis storefront core cartridge.

Steps to be followed:

  1. Create a folder splitit under sitegenesis-storefront-core-cartridge/cartridge/js
  2. Copy the file from split_sg_changes/cartridge/js/splitit/splititCheckout.js into sitegenesis-storefront-core-cartridge/cartridge/js/splitit/splititCheckout.js
SplititUpstreamMessaging.js

This is a new file that needs to be copied into the SiteGenesis storefront core cartridge.

Steps to be followed:

  1. Create a folder splitit under sitegenesis-storefront-core-cartridge/cartridge/js
  2. Copy the file from split_sg_changes/cartridge/js/splitit/splititUpstreamMessaging.js into sitegenesis-storefront-core-cartridge/cartridge/js/splitit/splititUpstreamMessaging.js
Custom_splitit.scss

This is a new file that needs to be copied into the SiteGenesis storefront core cartridge.

Steps to be followed:

  1. Copy the file from split_sg_changes/cartridge/scss/default/custom_splitit.scss into sitegenesis-storefront-core-cartridge/cartridge/scss/default/custom_splitit.scss

ISML Changes

Cart.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\checkout\cart\cart.isml

Code changes #1:

Add the following lines of code in orange as shown below

code changes

The changes should reflect as shown below:

show changes
Billing.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\checkout\billing\billing.isml

Code changes #1:

Add the following lines of code in orange as shown below:

billing.isml billing.isml 2

The changes should reflect as shown below:

show changes
Paymentmethods.isml

File location: sitegenesis-storefront-core- cartridge>>cartridge\templates\default\checkout\billing\paymentmethods.isml

Code changes #1:

Add the following lines of code in orange as shown below:

paymentmethods.isml paymentmethods.isml

The changes should reflect as shown below:

paymentmethods.isml changes

Code changes #2:

Add the following lines of code in orange as shown below:

paymentmethods.isml changes

The changes should reflect as shown below:

paymentmethods.isml changes
Minisummary.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\checkout\minisummary.isml

Code changes #1

Add the following lines of code in orange as shown below:

minisummary.isml

The changes should reflect as shown below:

minisummary.isml changes
Htmlhead.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\components\header\htmlhead.isml

Code changes #1

Add the following lines of code in orange as shown below:

htmlhead.isml

The changes should reflect as shown below:

htmlhead.isml changes
Homepage.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\content\home\homepage.isml

Code changes #1

Add the following lines of code in orange as shown below:

homepage.isml

The changes should reflect as shown below:

homepage.isml
Pricing.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\product\components\pricing.isml

Code changes #1

Add the following lines of code in orange as shown below:

pricing.isml

The changes should reflect as shown below:

pricing.isml changes

Code changes #2

Add the following lines of code in orange as shown below:

pricing.isml two

The changes should reflect as shown below:

pricing.isml changes two
Productsetproduct.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\product\components\productsetproduct.isml

Code changes #1

Add the following lines of code in orange as shown below:

productsetproduct.isml

The changes should reflect as shown below:

productsetproduct.isml changes
Productcontent.isml

File location: sitegenesis-storefront-core cartridge>>cartridge\templates\default\product\productcontent.isml

Code changes #1:

Add the following lines of code in orange as shown below:

productcontent.isml

The changes should reflect as shown below:

productcontent.isml
ProducttopcontentPS.isml

File location: sitegenesis-storefront-core-cartridge>>cartridge\templates\default\product\producttopcontentPS.isml

Code changes #1

Add the following lines of code in orange as shown below:

producttopcontentPS.isml

The changes should reflect as shown below:

producttopcontentPS.isml

User Guide

This section describes the various features offered by the cartridge that the merchant can leverage to promote Splitit on their website.

Custom CSS

A custom CSS file has been created within the cartridge which can be used by merchants to add CSS specific to Splitit banners or Flex Field widgets.

File Details: in int_splitit_sfra\cartridge\client\default\scss\custom_splitit.scss.

CSS added to the custom CSS file by the merchant will override the Splitit default CSS.

Upstream Messaging Banner

As part of the cartridge, the Upstream messaging banners have been implemented on the following pages

Homepage

messaging homepage

Footer

messaging footer

PDP, Cart, Checkout

messaging PDP, Cart, Checkout
Splitit Homepage Banner Slot

As part of the Splitit cartridge, a slot splitit-home-page-banner has been created which will render the following Upstream messaging banner. The slot uses the content asset splitit_homepage_banner to render the HTML.

messaging homepage banner

The following code within int_splitit_sfra\cartridge\templates\default\home\homePage.isml renders the slot. Please adjust the placement of the slot as per business requirements.

messaging homepage banner

As part of the Splitit cartridge, a content asset splitit_footer_banner has been created which will render the following Upstream messaging banner in the footer:

messaging footer banner
Messaging
Splitit Hosted Payment Method Tab Content

As part of the Splitit cartridge, a content asset splitit_hostedpayment_paymenttab_message has been created which holds the message to be displayed to the customer on the checkout page when they select the Splitit Hosted Payment option.

method tab content

If required, please update the messaging as per business requirements.

Splitit Payment Error Message

In the event of a failure during payment processing, the error message displayed to the customer is retrieved from:

int_splitit\cartridge\templates\resources\splitit.properties - payment.error.message

This message can be updated as per business requirements. Please note that the 0 within the existing message is a placeholder for supplementing the error message with the details returned from the API response.

Backend Operations

This section explains the various backend operations that merchants can leverage.

Refund Installments

The cartridge provides the ability for merchants to trigger refunds via code. As SFCC does not offer refund functionality as part of the OOB SFRA code, this code would need to be implemented wherever merchants need to trigger refunds.

Please use the following code to trigger a refund:

method tab content
Function ArgumentData TypeValue
orderdw.order.OrderSFCC Order object
refundInstallmentStrategyStringSplitit refund installment strategy. Please refer here for refund strategies available
refundAmountStringAmount to be refunded
Start Installments/Capture

For merchants who prefer to start the first installment on order shipment, the cartridge provides the ability for merchants to trigger the same.

Please use the following code to trigger capture the first installment:

start installments
Function ArgumentData TypeValue
orderdw.order.OrderSFCC Order object
Cancel Installment Plan

The cartridge provides the ability for merchants to trigger the cancellation of the installment plan via code.

Please use the following code to trigger the cancellation of the installment plan:

cancel installment plan
Function ArgumentData TypeValue
orderdw.order.OrderSFCC Order object
refundUnderCancellationStrategyStringSplitit refund installment strategy. Please refer here for refund strategies available
Update Installment Plan

When the basket total is updated after an installment plan is initiated, the Splitit installment plan needs to be updated with the new amount to ensure that the installments would be processed correctly.

The cartridge handles a view scenarios based on the OOB SFRA site however if the merchant website has other scenarios that could result in a change in basket total on the checkout, the following code could be utilized to trigger an update on the installment amount:

cancel installment plan
Demo page

The cartridge provides a customer BM module where developers/merchants can test the following actions:

  • Cancel Installment Plan
  • Refund Installments
  • Start Installments

Note: This module will only work on SIG instances and the primary purpose for this is for unit testing.

This section Splitit API Demo can be located within Merchant Tools > Splitit

splitit api demo

Testing

Checkout with Splitit Hosted Payment

This section outlines the Splitit Hosted Payment flow on the SiteGenesis storefront.

Prerequisites

  • Payment processor Splitit payment method must be configured as SPLITIT_HOSTED

Checkout Page – Billing section

On the billing step, if everything has been configured correctly, Splitit should appear as a payment method.

checkout page

Proceed to place the order once all the necessary details have been filled in.

Hosted page

Customers will be redirected to the Splitit Hosted payment page where they can provide their card details and select their preferred number of installments.

hosted page

Order confirmation page

Once the payment has been processed successfully, customers will be redirected to the Order confirmation page.

order confirmation page

Checkout with Splitit Flex Fields payment

This section outlines the Splitit Hosted Payment flow on the SiteGenesis storefront.

Prerequisites

  • Payment processor Splitit payment method must be configured as SPLITIT_FLEXFIELDS

Checkout Page – Billing section

On the billing step, if everything has been configured correctly, Splitit should appear as a payment method.

checkout page billing section

Proceed to place the order once all the necessary details have been filled in.

3DS page

If the merchant has enabled 3DS within the Splitit configurations and the customer’s credit card has been enrolled for 3DS, then an intermediate page would be shown to the customers where they need to provide the necessary details.

Customers will be redirected to the Splitit Hosted payment page where they can provide their card details and select their preferred number of installments.

checkout page billing section

Order confirmation page

Once the payment has been processed successfully, customers will be redirected to the Order confirmation page.

order confirmation page

Operations, Maintenance

Data Storage

Custom Objects

The following custom objects have been created as part of the integration.

  • SplititGeneralConfigurations
  • SplititInstallmentConfigurations
SplititGeneralConfigurations

This custom object holds all the Splitit related configuration details like

  • General details
  • Installments configuration
  • API related
  • Upstream messaging
Scopesite
Replicable?No
Retention Period0

At any given point in time, this will only always contain one record for each Site.

The records within this custom object are maintained by the custom BM module.

IMPORTANT: Records must not be manually created/updated within this custom object as this could result in unexpected results. Always use the custom BM module to configure the Splitit configurations which will internally update the custom objects.

Attribute IDData TypeDescription
isEnabledBooleanEnable/Disable Splitit
mailRecipientsSet of stringEmail address of the recipients in the event of API failure
apiKeyStringSplitit API key
apiUserNameStringSplitit API username
apiPasswordPasswordSplitit API password
splititEnvironmentEnum of stringMode of environment. Sandbox/Production
productBannerMinThresholdSet of stringMinimum threshold price required to display the Splitit banner on PDP
allowedPagesWithBannerEnum of stringConfigure the pages where Splitit upstream messaging banner displayed the
captureStrategyEnum of stringConfigure the auto-capture value
allowedPaymentCardTypesEnum of stringConfigure the Splitit allowed payment cards
is3DSEnabledBooleanEnable/Disable 3DS
SplititInstallmentConfigurations

This custom object holds details about the various installment options available for the customer based on their order total.

Scopesite
Replicable?No
Retention Period0

Each record within this custom object is a combination of

  • Installment range (lower limit)
  • Installment range (upper limit)
  • Currency

The records within this custom object are maintained by the custom BM module.

IMPORTANT: Records must not be manually created/updated within this custom object as this could result in unexpected results. Always use the custom BM module to configure the Splitit installment configurations which will internally update the custom objects.

Attribute IDData TypeDescription
currencyStringConfigure the currency code. E.g.: USD
amountFromIntegerConfigure the starting amount
amountToIntegerConfigure the maximum amount
numberOfInstallmentsSet of integersConfigure the number of installments
SplititWebhookNotifications

This custom object creates a record entry for every CreateSucceeded Webhook notification received from Splitit. The job SplititWebhookNotifications picks the custom object records and processes the notifications. Once the record is processed, the job deletes the record.

Scopesite
Replicable?No
Retention Period0
Attribute IDValuesDescription
typeStringType of the notification
notificationReceivedAtDatetimeNotification received time
encodedOrderNoStringEncoded order number
dataTextWhole response data
Custom Cache

The Splitit integration leverages the Custom Cache concept within Salesforce Commerce Cloud to retrieve the configuration data efficiently. The cache id for the custom cache created by the cartridge is called SplititCache.

For merchants who have disabled custom cache within Business Manager, the configuration data would be read directly from the custom object. This will not affect the functionality the performance will be slightly lower compared to using custom cache.

Note: When the customer changes the configuration against the payment methods in BM or updates the custom object directly then, the Splitit custom cache must be cleared. Splitit cache is automatically cleared when merchants use the custom BM module.

custom caches

Availability

In case of problems with the connection to Splitit Payments, please contact the Splitit Payments support department.

Please supply as much information as possible (Merchant account, time, order number, Splitit installment plan number etc.). Also, please check the log files.

Failover / Recovery Process

In case the Splitit service is unavailable, the user will not be able to checkout using Splitit payment methods and an error message would be displayed on the checkout pages.

The service availability can be tracked in SFCC using the Service Status.

Support

In case of problems with the integration, missing features, etc. please contact the Splitit Payments support department or your Splitit account manager.

Appendix

System Extensions

Order
IDPurpose
splitit_cancelAPIResponseStores the response of cancel API
splitit_createAPIResponseStores the response of create API
splitit_initiateAPIResponseStores the response of initiate API
splitit_installmentPlanNumberStores the installment plan number
splitit_publicTokenStores the public token generated by the Splitit
splitit_startInstallmentAPIResponseStores the response of start installment API
splitit_refundAPIResponseStores the response of refund API
splitit_verifyPaymentAPIResponseStores the response of verify payment API
Basket
IDPurpose
splitit_initiateAPIResponseStores the response of initiate API
splitit_installmentPlanNumberStores the installment plan number
splitit_publicTokenStores the public token generated by the Splitit
Locating code changes

Developers can locate code changes done for the Splitit integration by searching for the following comments pattern.

JS

// Splitit - Begin: {Text summarising the changes} 
Splitit code changes
// Splitit - End: {Text summarising the changes}

E.g.:

locating code changes

ISML

<iscomment> Splitit - Begin: Cart Upstream Messaging </iscomment>
<isinclude template="upstreammessaging/cart/splititCartBannerWrapper" />
<iscomment> Splitit - End: Cart Upstream Messaging </iscomment>

E.g.:

locating changes

Known Issues

None.

SFRA

Overview

The Splitit payment cartridge enables a commerce cloud store to integrate with the Splitit payment service. This document provides detailed instructions for installing the Splitit payment cartridge onto a commerce cloud store. The integration is based on the SFRA demo store, on version 5.1.0, provided by SFCC. The integration consists of an archive with contents as described in the below table.

NamePurpose
cartridgesContains Splitit integration cartridges
cartridges\int_splitit_sfraThis cartridge contains the SFRA specific changes required for Splitit integration
cartridges\int_splititThis cartridge contains the API calls for Splitit integration and common code extensions
cartridges\bm_splititThis cartridge contains Business Manager UI, BM-related system extensions to add/update general, API, payment, and upstream messaging configurations
cartridges\bm_splitit_demoThis cartridge contains BM-related system extensions for testing and validating payment flows (cancel, refund, and capture of charges). This cartridge will only work in Developer sandboxes.
metadataContains custom objects and settings required for the integration
documentationContains this document “Splitit SFRA Integration Document”

Features

The integration described in this document supports the following features:

  • Embedded card form checkout using Splitit Flex Fields payment
  • Hosted page checkout using Splitit Hosted payment.
  • Installment banners that have been implemented using Splitit Upstream Messaging
  • Ability to enable/disable the payment methods based on currency and country.
  • Ability to configure Splitit settings via a customer-friendly UI interface.

Splitit Flex Fields Payment

Splitit's Flex Fields is a unique product that allows you to fully integrate Splitit into the checkout process on your website, both stylistically and functionally. Flex Fields are individual iFrames plugged directly into the Splitit servers, however you can extensively customize them. For this customization, we have implemented an intermediate page for the checkout process.

Splitit Hosted Payment

Splitit's Hosted Payment Solution features a full redirect from the merchant site to Splitit's. To use it, fetch a URL from the Splitit API then send your customer there to enter credit card data. After the customer is done checking out, based on the outcome of the transaction, the customer is redirected to the appropriate endpoint within SFCC (success, cancel, or failure).

Splitit Upstream Messaging

Splitit's Upstream Messaging informs the customer early on in their journey on your website that Splitit will be available at checkout. It uses banners, price breakdowns, and Splitit messages that can be added to your home page, footer, product page, cart page, and checkout pages.

Payment Types Supported

Credit cards supported currently

  • Visa
  • Mastercard

Limitations, Constraints

Please check with Splitit to find out which languages are currently supported.

Compatibility

Compatible with Commerce Cloud Platform Release 21.2, SFRA 6.0.0.

Installation

Cartridges

Upload the following cartridge to the BM code version

  • int_splitit_sfra
  • int_splitit
  • bm_splitit
  • bm_splitit_demo (only on developer sandboxes)

Configure the cartridge path as shown in the below tables. Cartridges should be added to the beginning of the cartridge path.

Site Cartridge Pathint_splitit_sfra:int_splitit
BM Cartridge Pathint_splitit:bm_splitit:bm_splitit_demo

Metadata

All BM configurations related to the below components have been configured within metadata/site-template folder

  • System/Custom object definitions
  • Payment Methods
  • Payment Processors
  • Services
  • Jobs
  • Content

Please follow the below steps to import the BM configurations for the above-mentioned components

  1. Locate the folder metadata in the installation package.
  2. Review the contents within site-template folder.
  3. Change the site ID under path site-template\sites to your site ID.
  4. Change the library ID under path site-template\libraries to your library ID
  5. Archive the folder to ‘site-template.zip’ and the Import the file via Site Import & Export
Services

Two new services, “splitit.http.sandbox” and “splitit.http.production”, has been created as part of the integration.

Service IDService ProfileService Credential
splitit.http.sandboxsplitit.http.sandbox.profilesplitit.http.sandbox.credentials
splitit.http.productionsplitit.http.production.profilesplitit.http.production.credentials

The URLs for the sandbox and production endpoints have been configured within the cartridge.

EnvironmentURL
Non-production instanceshttps://webapi.sandbox.splitit.com/api
Production instanceshttps://webapi.splitit.com/api
Payment Processor

Two new payment processors have been created as part of the cartridge.

  • SPLITIT_FLEXFIELDS
  • SPLITIT_HOSTED
Payment Processor IDPurpose
SPLITIT_FLEXFIELDSPayment processor for processing transactions using the FlexFields (embedded card form) integration
SPLITIT_ HOSTEDPayment processor for processing transactions using the Hosted page (external redirection) integration
Payment Methods

A new payment method, Splitit has been created as part of the cartridge.

Jobs

A new job SplititWebhookNotifications has been created as part of the cartridge and is available under Administration > Operations > Jobs. This job processes the CreateSucceeded webhook notifications received from Splitit and processes them in recurring intervals.

Please follow the below steps to configure the job:

  1. Navigate to Administration > Operations > Jobs > SplititWebhookNotifications
  2. Select the Schedule and History tab.
  3. Check the Enabled checkbox.
  4. Set the Trigger as Recurring Interval
  5. Configure the start date and recurring interval duration. It is recommended that the recurring interval is >= 5 minutes.

The below image is for reference purpose only.

webhook notifications
  1. Click on the Job Steps tab.
  2. Click on Scope and select the relevant sites
select scope
Content

The following content assets have been created as part of the cartridge

  • splitit_homepage_banner
  • splitit_footer_banner
  • splitit_hostedpayment_paymenttab_message

The following content slots have been created as part of the cartridge

  • splitit-home-page-banner

Custom BM Module

A custom BM module has been developed to allow merchants to be able to configure all the Splitit related configurations in one place. This module has been developed using custom objects and not site preferences due to limitations around data replication and API availability for updating site preferences.

IMPORTANT: The custom objects are non-replicable. Hence please complete Splitit production configurations directly on the SFCC Production Instance itself. Configurations through this module cannot be replicated via data replication.

Please follow the below steps to provide permissions to view this BM module.

  1. Navigate to Administration > Organization > Roles & Permissions.
  2. Select the role that you would want to give access to the BM module.
  3. Select the Business Manager Modules tab.
  4. Select all the relevant sites where Splitit would be configured.
select sites
  1. Select the following modules from the popup and apply the changes
select modules
  1. Confirm that the following section is visible in the Merchant Tools overlay
merchant tools overlay section

Configurations

The below sections explain how to set up the Splitit integration-related configurations within Business Manager.

Payment Methods

Please refer to the below table while configuring the Splitit payment method.

Payment Method SettingValueDescription
Payment ProcessorSPLITIT_FLEXFIELDS OR SPLITIT_HOSTEDPlease select the relevant Payment Processor based on your mode of integration – FlexFields or Hosted
Min/Max Payment RangesDo not configureDo not configure the min/max payment ranges for currencies. This will be handled via a separate set of configurations.
CurrenciesBased on requirementsPlease configure the applicable currencies based on your requirements.
CountriesBased on requirementsPlease configure the applicable countries based on your requirements.

IMPORTANT: When any of the Payment Method settings have been modified, ensure that the Splitit custom cache is always cleared. Please refer to this link for more details regarding custom cache.

General Configurations

The General Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Enable Splitit On/OffControls whether the Splitit integration is enabled for the site
API failure email recipientsConfigure email addresses where notifications regarding email failure should be sent to.
general config

Splitit API Configurations

The API Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
API UsernameThis configuration is used within the Login API call which generates the Splitit session id. The value for this configuration can be retrieved from Splitit Dashboard > Credentials > Splitit Integration Credentials > API User Name
API PasswordThis configuration is used within the Login API call which generates the Splitit session id. The value for this configuration can be retrieved from Splitit Dashboard > Credentials > Splitit Integration Credentials > API User Password
API KeyThis configuration is set within the header of all the Splitit API calls (except Login). The value for this configuration can be retrieved from Splitit Dashboard > Credentials > Gateway Provider Credentials > Payment Terminal API Key
Splitit EnvironmentConfigure the Splitit environment this integration would use. On Production SFCC instances, this must be set to Production. On non-production SFCC instances, this must be set to Sandbox

The Check Credentials button when clicked validates the following

  • Format of API Key (does not check if the API key value is valid)
  • API User Name and API Password against the Splitit Environment selected
api configs

Splitit Payment Configurations

The Payment Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Enable 3DSThis configuration is used to enable/disable 3DS validation while processing payments.
Payment ActionThis configuration indicates whether the first installment must be captured on order placement or once the order is dispatched.
payment configs

Splitit Upstream Messaging Configurations

The Upstream Messaging Configurations section within Merchant Tools > Splitit allows merchants to configure the following

ConfigurationPurpose
Minimum amount to display the Splitit installment price on PDPThis configuration determines what is the minimum product price required to display the Upstream messaging banners on PDP. Currency-specific amounts can be set. All currencies enabled for the site will be listed here.
Upstream messaging selectionThis is a multi-select configuration with which merchants can decide which pages should display the Upstream Messaging Banner.
Footer allowed card brandsThis is a multi-select configuration that indicates which of the card brand logos must be displayed within the Footer upstream messaging banner. The values selected here would also be used to render the card logos shown against the Splitit payment method tab on the checkout page.
messaging configs

Splitit Installment Configurations

The Installment Configurations section within Merchant Tools > Splitit allows merchants to configure the following:

ConfigurationPurpose
Installment Configurations Min/Max currencyThis is a currency dropdown that lists all the currencies enabled on the site. Merchants can configure currency-specific installment ranges and the applicable number of installments by selecting the currency from this dropdown.
Amount FromIndicates the lower limit of the order total range.
Amount ToIndicates the upper limit of the order total range.
No. of InstallmentsComma-separated list of installment options to be presented to the customer on the checkout page for the particular range

Steps to be followed while configuring installment range and options:

  1. Pre-determine the different order total ranges and the number of installments to be presented to the customers on the checkout page.
  2. Select the currency from the currency dropdown.
  3. Using the Add button creates an entry for the range.
  4. Enter the lower amount of the order total range within the Amount From column
  5. Enter the upper amount of the order total range within the Amount To column
  6. Enter the number of installments to be presented to the customers for this particular order total range.
  7. Repeat steps 4 – 6 if more than one range is applicable as per business requirements.
  8. Click on Save
  9. Repeat steps 1 – 8 for other currencies (if applicable)
installment configs

User Guide

This section describes the various features offered by the cartridge that the merchant can leverage to promote Splitit on their website.

Custom CSS

A custom CSS file has been created within the cartridge which can be used by merchants to add CSS specific to Splitit banners or flex field widgets.

File Details: in int_splitit_sfra\cartridge\client\default\scss\custom_splitit.scss.

CSS added to the custom CSS file by the merchant will override the Splitit default CSS.

Upstream Messaging Banner

As part of the cartridge, the Upstream messaging banners have been implemented on the following pages:

Homepage
banner footer
PDP, Cart, Checkout
pdp cart checkout
Splitit Homepage Banner Slot

As part of the Splitit cartridge, a slot splitit-home-page-banner has been created which will render the following Upstream messaging banner. The slot uses the content asset splitit_homepage_banner to render the HTML.

banner

The following code within int_splitit_sfra\cartridge\templates\default\home\homePage.isml renders the slot. Please adjust the placement of the slot as per business requirements.

<iscomment> Splitit - Begin: Homepage Upstream Messaging </iscomment> 
<isinclude template="upstreammessaging/homepage/splititHomePageBanner" />
<iscomment> Splitit - End: Homepage Upstream Messaging </iscomment>

As part of the Splitit cartridge, a content asset splitit_footer_banner has been created which will render the following Upstream messaging banner in the footer.

footer
Messaging
Splitit Hosted Payment Method Tab Content

As part of the Splitit cartridge, a content asset splitit_hostedpayment_paymenttab_message has been created which holds the message to be displayed to the customer on the checkout page when they select the Splitit Hosted Payment option.

payment tab content

If required, please update the messaging as per business requirements.

Splitit Payment Error Message

In the event of a failure during payment processing, the error message displayed to the customer is retrieved from:

int_splitit\cartridge\templates\resources\splitit.properties - payment.error.message

This message can be updated as per business requirements. Please note that the 0 within the existing message is a placeholder for supplementing the error message with the details returned from the API response.

Backend Operations

This section explains the various backend operations that merchants can leverage.

Refund Installments

The cartridge provides the ability for merchants to trigger refunds via code. As SFCC does not offer refund functionality as part of the OOB SFRA code, this code would need to be implemented wherever merchants need to trigger refunds.

Please use the following code to trigger a refund:

// Splitit-Begin: Trigger refund 
var splititServices = require('int_splitit/cartridge/scripts/services/splititServices');
var apiResponse = splititServices.refund(order, refundInstallmentStrategy, refundAmount);
// Splitit-End: Trigger refund
Function ArgumentData TypeValue
orderdw.order.OrderSFCC Order object
refundInstallmentStrategyStringSplitit refund installment strategy. Please refer to https://developers.splitit.com/api/v3/refund-a-plan for refund strategies available
refundAmountStringAmount to be refunded
Start Installments / Capture

For merchants who prefer to start the first installment on order shipment, the cartridge provides the ability for merchants to trigger the same. s Please use the following code to trigger capture the first installment:

// Splitit-Begin: Trigger capture / start installment 
var splititServices = require('int_splitit/cartridge/scripts/services/splititServices');
var apiResponse = splititServices.startInstallment(order);
// Splitit-End: Trigger capture / start installment

Function ArgumentData TypeValue
orderdw.order.OrderSFCC Order object
Cancel Installment Plan

The cartridge provides the ability for merchants to trigger the cancellation of the installment plan via code.

Please use the following code to trigger the cancellation of the installment plan:

// Splitit-Begin: Trigger Cancel Installment Plan 
var splititServices = require('int_splitit/cartridge/scripts/services/splititServices');
var apiResponse = splititServices.cancel(order, refundUnderCancellationStrategy);
// Splitit-End: Trigger Cancel Installment Plan
Function ArgumentData TypeValue
orderdw.order.OrderSFCC Order object
refundUnderCancellationStrategyStringRefund strategy to be used when canceling the installment plan. Please refer to https://developers.splitit.com/api/v3/refund-a-plan for possible values.
Update Installment Plan

When the basket total is updated after an installment plan is initiated, the Splitit installment plan needs to be updated with the new amount to ensure that the installments would be processed correctly.

The cartridge handles a view scenarios based on the OOB SFRA site however if the merchant website has other scenarios that could result in a change in basket total on the checkout, the following code could be utilised to trigger an update on the installment amount.

//Splitit-Begin: Update installment amount on plan 
$('body').trigger('splitit:updateInstallmentAmount');
//Splitit-End: Update installment amount on plan
Demo page

The cartridge provides a customer BM module where developers/merchants can test the following actions

  • Cancel Installment Plan
  • Refund Installments
  • Start Installments

Note: This module will only work on SIG instances and the primary purpose for this is for unit testing. This section Splitit API Demo can be located within Merchant Tools > Splitit

splitit api demo

Testing

Checkout with Splitit Hosted payment

This section outlines the Splitit Hosted Payment flow on the RefArch storefront.

Prerequisites

  • Payment processor Splitit payment method must be configured as SPLITIT_HOSTED.

Checkout Page – Billing section

On the billing step, if everything has been configured correctly, Splitit should appear as a payment method.

checkout page

Proceed to place the order once all the necessary details have been filled in.

Hosted Page

Customers will be redirected to the Splitit Hosted payment page where they can provide their card details and select their preferred number of installments.

hosted page

Order Confirmation Page

Once the payment has been processed successfully, customers will be redirected to the Order confirmation page.

order confirmation page

Checkout with Splitit Flex Fields payment

This section outlines the Splitit Flex Fields Payment flow on the RefArch storefront.

Prerequisites

  • Payment processor Splitit payment method must be configured as SPLITIT_FLEXFIELDS.

Checkout Page – Billing section

On the billing step, if everything has been configured correctly, Splitit should appear as a payment method.

splitit payment method

Proceed to place the order once all the necessary details have been filled in.

3DS Page

If the merchant has enabled 3DS within the Splitit configurations and the customer’s credit card has been enrolled for 3DS, then an intermediate page would be shown to the customers where they need to provide the necessary details.

Customers will be redirected to the Splitit Hosted payment page where they can provide their card details and select their preferred number of installments.

3ds

Order confirmation page

Once the payment has been processed successfully, customers will be redirected to the Order confirmation page.

order confirmation page

Operations, Maintenance

Data Storage

Custom Objects

The following custom objects have been created as part of the integration.

  • SplititGeneralConfigurations
  • SplititInstallmentConfigurations
SplititGeneralConfigurations

This custom object holds all the Splitit related configuration details like

  • General details
  • Installments configuration
  • API related
  • Upstream messaging
ScopeSite
Replicable?No
Retention Period0

At any given point in time, this will only always contain one record for each Site.

The records within this custom object are maintained by the custom BM module.

IMPORTANT: Records must not be manually created/updated within this custom object as this could result in unexpected results. Always use the custom BM module to configure the Splitit configurations which will internally update the custom objects.

Attribute IDData TypeDescription
isEnabledBooleanEnable/Disable Splitit
mailRecipientsSet of stringEmail address of the recipients in the event of API failure
apiKeyStringSplitit API key
apiUserNameStringSplitit API username
apiPasswordPasswordSplitit API password
splititEnvironmentEnum of stringMode of environment. Sandbox/Production
productBannerMinThresholdSet of stringMinimum threshold price required to display the Splitit banner on PDP
allowedPagesWithBannerEnum of stringConfigure the pages where Splitit upstream messaging banner displayed the
captureStrategyEnum of stringConfigure the auto-capture value
allowedPaymentCardTypesEnum of stringConfigure the Splitit allowed payment cards
is3DSEnabledBooleanEnable/Disable 3DS
SplititInstallmentConfigurations

This custom object holds details about the various installment options available for the customer based on their order total.

ScopeSite
Replicable?No
Retention Period0

Each record within this custom object is a combination of

  • Installment range (lower limit)
  • Installment range (upper limit)
  • Currency

The records within this custom object are maintained by the custom BM module.

IMPORTANT: Records must not be manually created/updated within this custom object as this could result in unexpected results. Always use the custom BM module to configure the Splitit installment configurations which will internally update the custom objects.

Attribute IDData TypeDescription
currencyStringConfigure the currency code. E.g.: USD
amountFromIntegerConfigure the starting amount
amountToIntegerConfigure the maximum amount
numberOfInstallmentsSet of integersConfigure the number of installments
SplititWebhookNotifications

This custom object creates a record entry for every CreateSucceeded Webhook notification received from Splitit. The job SplititWebhookNotifications picks the custom object records and processes the notifications. Once the record is processed, the job deletes the record.

ScopeSite
Replicable?No
Retention Period0
Attribute IDValuesDescription
typeStringType of the notification
notificationReceivedAtDatetimeNotification received time
encodedOrderNoStringEncoded order number
dataTextWhole response data
Custom Cache

The Splitit integration leverages the Custom Cache concept within Salesforce Commerce Cloud to retrieve the configuration data efficiently. The cache id for the custom cache created by the cartridge is called SplititCache.

For merchants who have disabled custom cache within Business Manager, the configuration data would be read directly from the custom object. This will not affect the functionality the performance will be slightly lower compared to using custom cache.

Note: When the customer changes the configuration against the payment methods in BM or updates the custom object directly then, the Splitit custom cache must be cleared. Splitit cache is automatically cleared when merchants use the custom BM module.

custom caches

Availability

In case of problems with the connection to Splitit Payments, please contact the Splitit Payments support department.

Please supply as much information as possible (Merchant account, time, order number, Splitit installment plan number etc.). Also, please check the log files.

Failover / Recovery Process

In case the Splitit service is unavailable, the user will not be able to checkout using Splitit payment methods and an error message would be displayed on the checkout pages.

The service availability can be tracked in SFCC using the Service Status.

Support

In case of problems with the integration, missing features, etc. please contact the Splitit Payments support department or your Splitit account manager.

Appendix

System extensions

In addition to the changes mentioned above, the below system extensions were done as part of the cartridge.

Order
IDPurpose
splitit_cancelAPIResponseStores the response of cancel API
splitit_createAPIResponseStores the response of create API
splitit_initiateAPIResponseStores the response of initiate API
splitit_installmentPlanNumberStores the installment plan number
splitit_publicTokenStores the public token generated by the Splitit
splitit_startInstallmentAPIResponseStores the response of start installment API
splitit_refundAPIResponseStores the response of refund API
splitit_verifyPaymentAPIResponseStores the response of verify payment API
Basket
IDPurpose
splitit_initiateAPIResponseStores the response of initiate API
splitit_installmentPlanNumberStores the installment plan number
splitit_publicTokenStores the public token generated by the Splitit
Locating code changes

Developers can locate code changes done for the Splitit integration by searching for the following comments pattern.

JS

// Splitit - Begin: <<Text summarizing the changes>>
Splitit code changes
// Splitit - End: <<Text summarizing the changes>>

E.g.:

// Splitit - Begin: if payment method is splitit class added to input fields 
if (paymentMethodID === 'Splitit') {
$('#splititFlexFieldsFormHiddenCheckbox').removeClass('splitit-form-checkbox-display');
$('.payment-method-expanded').filter('[data-method="Splitit"').removeClass('splitit-d-none');
} else {
$('#splititFlexFieldsFormHiddenCheckbox').addClass('splitit-form-checkbox-display');
}
// Splitit - End: if payment method is splitit class added to input fields

ISML

E.g.:

<iscomment> Splitit - Begin: Cart Upstream Messaging </iscomment>
<isinclude template="upstreammessaging/cart/splititCartBannerWrapper" />
<iscomment> Splitit - End: Cart Upstream Messaging </iscomment>

Known Issues

None.

Videos

Splitit Metadata

Configuring Business Manager

Configuring Splitit Business Manager Module

Enable Flex Fields Integration Mode

Enable Hosted Integration Mode

Clearing Splitit Custom Cache

Splitit Integration Document

SiteGenesis Integration Guide