1. One-time card payments (Online)
Kushki Docs
English
  • Español
  • English
  • Home
  • Quick Start
    • Frequently Asked Questions
    • Moving to Production
    • Policy for Important API Changes
    • Test Data
    • Error Codes
    • Latest Features
  • Payment Glossary
    • Payments Glossary
  • One-time card payments (Online)
    • Supported card brands
    • Functionalities by business model
    • How do third party commissions work?
    • Integration guide Third Party Commissions
    • Network Tokens
    • One-step Payments
      • How do Card Payments Work?
      • Accept a Card Payment
      • Direct charge (without token)
      • Accept One-Time Payments with OTP
      • OTP Authentication Error Codes
      • Error codes for single card payments
    • Two-steps Payments
      • How do single payments with authorization and capture work?
      • Receive payments with authorization and capture
    • Refunds
      • Returns, cancellations, and refunds
    • 3DS Authentication
      • Introduction to 3DS
      • 3DS API integration
      • 3DS integration with kushki.js library
      • 3DS API integration plus kushki.js library
      • 3DS Error Codes
    • Apple Pay Payments
      • Apple Pay Configuration
      • Apple Pay Sandbox testing
  • Recurring Card Payments (Online)
    • Functionalities by business model
    • External subscriptions to Kushki
    • Authenticate your subscriptions with 3DS
    • Accept one-click payments with 3DS
    • Error codes in recurring charges
    • Apple Pay for Subscriptions
    • Scheduled payments
      • How do Credit or Debit Card Payment Recurring Charges Work?
      • Create a recurring charge
      • Manage your Scheduled Charges
    • OneClick Payments
      • Accepting One-Click Payments
      • How do OneClick payments with authorization and capture work?
      • Receive one-click payments with authorization and capture
  • Card-present payments
    • Card present payments
    • Accept card present payments
    • Test data
    • Webhooks for card present
    • Cloud Terminal API
      • Cloud terminal API overview
      • Take payments
      • Cancel a payment request
      • Check the status of a payment request
      • How to print a customized ticket?
    • App-to-app
      • App-to-app overview
      • Take payments
    • Terminal SDK
      • Terminal SDK Introduction
      • Take payments
    • Raw card-present API
      • Raw card-present API overview
      • Cryptographic key exchange
      • Sample script to encrypt information
      • Take Payments
      • Frequently Asked Questions
      • Error codes for card-present transactions
    • Transactions
      • Transactions
      • Cancel payments
    • Kushki One
      • First Steps
      • Autenticación y Cifrado de Requests
      • Accept payments with Kushki One
      • Amount Format
      • Async services and webhooks
      • Printing on SmartPOS terminal
      • Unified Error Catalog — Kushki ONE Connect
    • Kushki One Payment App
      • Overview
      • Process a payment
      • Split payment on the terminal
      • Refunds and PreAuth & Capture
      • Review Your Transactions
      • Terminal Setup
  • Wire Transfers
    • How do Payments by Wire Transfers Work?
    • Banks and transaction details for bank transfer payments
    • Receive Wire Transfers
    • Check the Status of a Transaction
  • Money Disbursement
    • Wire Transfer
      • How Does a Payment Distribution by Wire Transfer Work?
      • Payment Distribution to Bank Accounts
      • Error codes for transfer dispersions
  • Payment Links
    • Smartlinks
  • Plugins
    • Shopify
      • Shopify
      • Plugin Operation
    • VTEX
      • VTEX Integration Guide
  • Payment forms and buttons
    • Kajita
      • How Does it Work?
      • Payment Kajitas
    • Payment Button
      • Overview
      • Generate a payment button
  • Branch Offices Management
    • How to Onboard Submerchants via API
  • Notifications
    • Webhooks
    • Good Practices
    • Check your Webhooks
    • One-time Payments Webhooks
      • Webhook for One-Time Payments made with a card
      • Webhook for One-Time Payments by Wire Transfer
      • Webhook for One-Time Payments in Cash
    • Recurring Payments Webhooks
      • Webhook for Recurring Payments Made with Card
    • Payment Distribution Webhooks
      • Webhook for payment disbursement through wire transfer
    • Payment button Webhooks
      • Webhooks with Payment Button
    • Smartlinks Webhooks
      • Webhooks with Smartlinks
    • Refunds Webhooks
      • Webhook for Voids and Refunds
      • Chargeback Webhooks
HomeMexico 🇲🇽
Ecuador 🇪🇨Chile 🇨🇱Colombia 🇨🇴Peru 🇵🇪
HomeMexico 🇲🇽
Ecuador 🇪🇨Chile 🇨🇱Colombia 🇨🇴Peru 🇵🇪
Status
Soporte / Support
English
  • Español
  • English
  1. One-time card payments (Online)

Integration guide Third Party Commissions

Product in beta version 🔐👨‍
We are working on our beta version. Stay tuned for its official release! You can also contact your account manager for more information.

Enable third-party commissions for your merchant.#

To enable Third Party Commissions feature in your merchant, you mustsubmit a request through our support center with the following information:
Email
Merchant ID or Name
How can we help you? (Other)
Business Impact (Limited)
Subject (Enable Third-Party Commissions feature)
Description (Add detailed information about the request)
Country
Once the form is submitted, you need confirmation that the feature has been enabled.

Perform the integration to accept third-party commissions#

If you have ready your integration with Kajita or Kushki.js, you can skip this step.
To use the Third-Party Commissions feature, you need to integrate our frontend solutions (Kajita or Kushki.js) and link them to your backend. For this, you can check our guide Accept a card payment.

Review your Third-Party Commissions configuration#

Validate if the service is active and obtain information related to the commission charges configured for your business using the getCommissionConfiguration method in Kushki.js or the Get Commission Configuration endpoint of our API. It is necessary to integrate one of these options depending on your integration type to display a breakdown to the end user with the amounts to be charged.

getCommissionConfiguration() Method in Kushki.js#

Validate the configured information for your business and display a breakdown for Third-Party Commissions by consulting the getCommissionConfiguration method from Kushki.js in case you have implemented the kushki.js library. Below is an example:
Request
Required parameters
totalAmount: Send the amount for which you want to know the commission to be charged (e.g., $100)
currency: Send the currency configured in your merchant
Response
Once the getCommissionConfiguration method is consumed , a similar response to the following will be returned:
{
    "commissionMerchantName": "Merchant commissions",
    "parentMerchantName": "Fintech Global",
    "amount": {
        "currency": "USD",
        "iva": 0,
        "subtotalIva": 4,
        "subtotalIva0": 0
    },
    "merchantId": "20000000103814111000",
    "totalAmount": 4
}
Where
commissionMerchantName: It is the merchant's name that will receive the commission
parentMerchantName: It is the main merchant's name
amount: The amount object indicates the commission amount based on the rules configured in the main merchant.
merchantId: Refers to the merchant ID that will receive the commission.
totalAmount: It is the total commission amount to be charged, which must be added to the original (in the previous example 4 for the commission = $104)
For example, if the main merchant has a 4% commission configured per transaction and a 100 for the original sale plus 104 in total). Thus, the main merchant will receive 4, which corresponds to the amount returned by the totalAmount field.

Get Commission configuration Endpoint via API#

It is necessary to consume the Get Commission Configuration endpoint from our Online Payments API to obtain the configuration information for Third-Party Commissions in your merchant as well as the commission to be charged, allowing you to display the breakdown to the end customer on the payment screen. Below is an example:
Request
{
  "totalAmount": 100,
  "currency": "USD"
}
Response
{
    "commissionMerchantName": "Merchant commissions",
    "parentMerchantName": "Fintech Global",
    "amount": {
        "currency": "USD",
        "iva": 0,
        "subtotalIva": 4,
        "subtotalIva0": 0
    },
    "merchantId": "20000000103814111000",
    "totalAmount": 4
}
Where
commissionMerchantName: It is the merchant's name that will receive the commission
parentMerchantName: It is the main merchant's name
amount: The amount object indicates the commission amount based on the rules configured in the main merchant.
merchantId: Refers to the merchant ID that will receive the commission.
totalAmount: It is the total commission amount to be charged, which must be added to the original (in the previous example 4 for the commission = $104).

Considerations on voids with third-party commissions#

When using the split payments functionality, the behavior of the void depends on the type of reversal performed:
Full void: Both the transaction amount and the commission are refunded.
Partial void: Only the transaction amount is refunded. The commission is not refunded.
This behavior is important to avoid accounting inconsistencies or reconciliation errors. Make sure to assess whether the reversal should include the commission as well—if so, perform a full void.
Modificado en 2026-10-14 19:42:15
Anterior
How do third party commissions work?
Siguiente
Network Tokens
Built with