Splitit

Disclaimers:

No card details are stored for merchants using Splitit

Splitit will only work for one-time purchases only. Splitit will NOT work with standard recurring billing/subscriptions. All installment billing will be managed by Splitit.

Splitit will work with Checkout Champ hosted pages and landers that connect via Direct API. This will not work via Order Entry.

Splitit does not support a traditional Auth/Capture billing model

The order of operations with Splitit are as follows:

  • An initial order is sent to Splitit

  • Splitit returns a Checkout URL

  • The browser is redirected to the Checkout URL

  • The consumer chooses a payment plan at Splitit, entering card number and selecting the installment schedule

  • When complete, Splitit notifies Checkout Champ to finalize the order

  • The browser is redirected to the first upsell page (this is optional, perhaps there are no upsells)

    • When the consumer submits each upsell page a request is made to Splitit to update the installment plan. There is no consumer interaction with Splitit for this.

  • When the order is complete Checkout Champ sends a request to capture the first installment of the total amount (initial order + all upsells). For example, if a consumer purchased a $100 item, chose 4 installments, and then purchased a $20 upsell, the initial capture will be for $30.

  • The entire order is saved in Checkout Champ with all items. There is one transaction for the initial sale and one for each upsell.

  • Splitit controls billing the remaining installments. There is no rebilling in Checkout Champ. Checkout Champ is not notified of the results of each installment billing at Split.

  • Refunds can be triggered using standard Checkout Champ functionality. A refund is given at Splitit using the unbilled installments first. For example, if a $120 item is billed in 4 installments and the consumer has paid 2 installments and the consumer is given a 75% ($90) refund, then the 2 unbilled installments take up $60 of the refund and the remaining $30 is refunded to the card for charges paid. It is recommended to only give full order refunds on Splitit since Checkout Champ has no window into how many installments have been paid. It is not recommended to refund individual transactions.

STEP 1

Go to Gateways | Gateway Integrations and select the Splitit tile. Click on +Activate.

Obtain clientId, clientSecret, and terminalKey from Splitit. Enter those values here.

Choose to attempt 3DS Secure processing at Splitit using the force3DS option

Click the green Create Gateway button to save changes and create the gateway

STEP 2

If Splitit is your only gateway option, assign the gateway to the campaign offers and upsells. If you are using Splitit as an additional payment option, use the forceMerchantId parameter in the Import Order API call when the customer submits their order with the Splitit payment button. Note that this will only work for one time sales, it will not work with recurring transactions.

STEP 3

The checkout page must be secure HTTPS. A non-secured call to the Splitit gateway will be rejected.

Include paySource=PREPAID and prepaidType=SPLITIT on the Import Order API call from the checkout page. Do not pass any other card information.

One option is to use hidden input fields on the page

<input type="hidden" name='paySource' value="PREPAID">
<input type='hidden' name='prepaidType' value='SPLITIT'>

For more info on the API call, please refer to our API Documentation.

STEP 4 - Redirect

Follow standard 3Ds instructions to redirect the consumer to Splitit

Direct API 3DS Instructions

STEP 5 - Upsells

Upsells require no special processing. Pass in the Import Upsale API call using standard parameters. Each upsell is added to the installment plan at Splitit.

Last updated