Split Payments

Embedded Payments allows you to split each payment with your merchants, in which case you can control the specific split details.

Split Payments

Use platform split payments to route part of a captured transaction to your platform and the remaining funds to a merchant.

BlueSnap works with you to define your platform split structure. At capture, BlueSnap routes the split amount to your platform and the remaining funds to the merchant. BlueSnap's processing fees are deducted from the merchant's side of the transaction, meaning that the merchant payout will be less than the total amount the shopper paid.

📘

Revenue share is handled separately!

Revenue share is managed separately through your BlueSnap commercial agreement. Depending on your commercial setup, your platform can use revenue share, split payments, or both.

Use split payments when part of a captured transaction needs to be routed to your platform at capture. Use revenue share when BlueSnap pays your platform outside individual transaction flow.

Split Payments in API Requests

BlueSnap must first enable split payments for your platform and provide your platform vendorId.

Then, use the vendorsInfo container to include the platform split amount in payment requests such as Auth Capture, Auth Only, Capture, and supported alternative payments:

  • The vendorId identifies your platform account, not the merchant receiving the remaining funds. BlueSnap assigns this value during implementation.
  • The platform split amount is the amount routed to your platform from the captured transaction. In BlueSnap API fields, this amount is the vendor commission. Use commissionPercent when your platform split is a percentage of the transaction amount, and commissionAmount when your platform split is a fixed amount.

In the following example, the shopper pays $1,050. BlueSnap allocates $30 to the platform vendor and the remaining transaction amount to the merchant side before fees.

curl -v -X POST https://sandbox.bluesnap.com/services/2/transactions \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d '
{ 
  "amount": 1050, 
  "currency": "USD", 
  "cardTransactionType": "AUTH_CAPTURE", 
  "vendorsInfo": { 
    "vendorInfo": [ 
      { 
        "vendorId": "10398032", 
        "commissionAmount": 30 
      } 
    ] 
  }
}'
curl -v -X POST https://sandbox.bluesnap.com/services/2/transactions \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d '
{ 
  "vendorsInfo": { 
  "vendorInfo": [ 
      { 
        "vendorId": "10398032", 
        "commissionPercent": 3 
      } 
    ] 
  } 
}'

Refunds with Split Payments

When refunding a transaction that included a platform split amount, BlueSnap determines how much of the refund is taken from the merchant side and how much is taken from the platform vendor side. Unless an override is provided, BlueSnap calculates the refund using the original vendor commission split.

BlueSnap processing fees are handled according to your BlueSnap commercial setup. Before going live, review refund behavior so your platform understands whether the platform split amount is refunded, partially refunded, or retained for each refund scenario.

📘

For chargebacks, BlueSnap debits the merchant and your platform for their respective portions of the chargeback amount. Any chargeback fees are charged to the merchant.

Refund Example

In this scenario, the shopper-facing platform fee is $50. The platform uses that additional shopper-paid amount to offset the $20 BlueSnap processing fee and route $30 to the platform as the platform split amount.

  • Shopper paid $1,050
  • Merchant sale amount: $1,000
  • Shopper-facing platform fee: $50
  • BlueSnap processing fee: $20
  • Merchant net payout: $1,000
  • Platform split amount: $30

Override the Platform Split

If you need to override the platform split portion of the refund, include vendorsRefundInfo in the Refund API request. This lets your platform control whether the platform split is refunded, partially refunded, or retained, depending on your refund policy and implementation.

In this example, the refund amount is $100 and $5 is associated with the platform vendor:

curl -v -X POST https://sandbox.bluesnap.com/services/2/transactions/refund/1039287689 \
-H 'Content-Type: application/json' \
-H 'Accept: application/json' \ 
-H 'Authorization: Basic dXNlcm5hbWU6cGFzc3dvcmQ=' \
-d '
{ 
  "amount": 100, 
  "vendorsRefundInfo": { 
    "vendorRefundInfo": [ 
      { 
        "vendorId": "10398032", 
        "vendorAmount": 5 
      } 
    ] 
  } 
}'

Implementation Checklist

Before going live:

  1. Confirm your split structure with BlueSnap.
  2. Use the vendorId assigned to your platform account.
  3. Send the platform split amount in supported payment requests.
  4. Distinguish merchant sale amount, platform split amount, BlueSnap processing fees, merchant payouts, and platform payouts in your internal reporting.
  5. Do not use surcharges as platform revenue or monetization. Use surcharge flows only when reviewed and approved for your use case, and only to recover applicable BlueSnap processing fees.
  6. Review processing fee, payout, and refund behavior with BlueSnap before going live.