Skip to main content

Features

Overview​

Checkouts offer consolidated payment collection, payment method tokenization into groups, and customizable application fees in a single workflow. Supported payment types include Card Payments, ACH Payments, Insurance Quote Payments, BNPL (Buy Now Pay Later) Payments (API support pending), and Terminal (Card Reader) Payments.

note: New features will be documented here as they become available.

Card and ACH Payment​

  • To process a card or ACH payment through this API, refer to Checkout via API
  • To process a card or ACH payment using the Unified Fintech Checkout™ Component, refer to Checkout via Component

Insurance Quote Payments​

BNPL Payments​

note: Disable the BNPL option by passing the correspondent prop to the web component: disable-bnpl

Terminal (Card Reader) Payments​

  • For terminal payments, contact customer_success@justifi.tech to enable the card-present feature. JustiFi will then provision and configure terminals for your sub accounts.
  • Find detailed steps in the Terminals API

Fees​

Checkouts support flexible fee structures that allow you to specify different fee types. This enables transparent reporting for merchants and selective fee refunds.

Use the payment.fees parameter to specify fee types when creating a checkout:

{
  "amount": 10000,
  "description": "order_xyz",
  "payment": {
    "fees": [
      { "type": "processing_fee", "amount": 295 },
      { "type": "platform_fee", "amount": 150 }
    ]
  }
}

Supported fee types:

  • processing_fee - Fees related to payment processing costs
  • platform_fee - Fees for your platform's services

Benefits of using the fees array:

  • Transparent reporting: Each fee type appears as a separate line item in merchant balance transactions
  • Selective refunds: When processing refunds, you can choose which fees to return to the merchant

For full documentation, see Enhanced Fee Management.

Application Fees​

For Existing Integrations

The application_fees parameter continues to work for existing integrations. New integrations should use payment.fees instead for selective refund support.

  • Application Fees are configured at the Platform level and can be customized for specific sub accounts. Checkouts add an additional layer of flexibility by allowing the use of the application_fees parameter when creating a checkout.

  • Create a Checkout: Use the Create Checkout API with custom application fees (in cents) for card and bank payments, as in the following example:

{
  "amount": 1000,
  "description": "test checkout application fees",
  "application_fees": {
    "card": {
      "amount": "200"
    },
    "bank_account": {
      "amount": "100"
    }
  }
}
  • The application fee applies based on the selected payment method during checkout. It overwrites the application_fee_rate set for the sub account. note: available for Card, ACH and Terminal (Card Present) only!

Important: You cannot use both application_fees and fees in the same request.

Payment Method Group​

  • Create a Payment Method Group: Use the Payment Method Group API to create a group for easy payment method access.
  • Create a Checkout: Use the Create Checkout API and pass the payment_method_group_id.
  • Checkout Web Component: Use the Unified Fintech Checkout™ Component and pass the checkout id. This allows the component to display a list of tokenized payment methods in the group, and an option to Save new payment method is also available.