Split Payments

  • Published on Apr 16, 2025
  • 5 minute(s) read
Prev Next

Split Payments allows users to define how to reconcile funds from different purchases (e.g., Tickets, Donations, Products) to specific gateway accounts connected to separate bank accounts.

The benefits of using Split Payments include the following.

  • Allow Attendees to pay using both a primary Payment Gateway and a Donation Payment Gateway during a single checkout experience.
  • Improve the user experience by eliminating the need to enter payment details multiple times.

New Fields

Three new payment gateway-related lookup fields are now available in addition to the existing Event object’s Payment Gateway and Payment Gateway object’s Default fields.

  • Object: Event
    • Field Label: Donation Payment Gateway
    • API Name: conference360__Donation_Payment_Gateway__c
    • Data Type: Lookup
    • Description: Use this field to configure a separate Payment Gateway that will process only Donations at a paid Event. Note: The gateway selected must use the same payment processor as the default Payment Gateway for the Event.
  • Object: Event Item
    • Field Label: Payment Gateway
    • API Name: conference360__Payment_Gateway__c
    • Data Type: Lookup
    • Description: This Payment Gateway will process this Event Item. If blank, the default Payment Gateway for the Event will be used.
  • Object: Payment Gateway
    • Field Label: Default Donation Gateway
    • API Name: conference360__Default_Donation_Gateway__c
    • Field Type: Checkbox
    • Description: If checked and Split Payments is enabled, this gateway will be used as the Donation Gateway for Events.

When separating Donations from the other Event Items, Donations will use the Event’s Donation Payment Gateway, and all other Event Items will use the standard Payment Gateway on the Event record.

If you want to designate a default donation gateway, use the Payment Gateway’s Default Donation Gateway field.

Use the Payment Gateway’s Default field for all other Event Items.

New Custom Setting

The new Blackthorn | Events Settings custom setting, Enable Split Donation Payments, turns on the Split Payments feature, which separates Donations from other Event Items. When enabled, Donations are funneled into their own gateway account and each Donation has its own Transaction that is separate from the other Event Items.

This setting also means users can stop manually reconciling funds from a single bank account, where the Transaction is paid, into separate bank accounts.

  • Location: Custom Settings > Blackthorn | Events Settings
  • Field Label: Enable Split Donation Payments
  • API Name: conference360__Enable_Split_Donations_Payments__c
  • Type: Checkbox
  • Default Value: False (not checked)
  • Description: Enable this setting to configure a second gateway account to separate Donations from other Event Items.

How It Works

If Enable Split Donation Payments is enabled, the following will occur.

  • Event Items with Type = “Main event ticket,” “Guest,” and “Other” (Products) will be assigned to the Event’s (primary) Payment Gateway.
  • Event Items with Type = “Donation” will be assigned to the Event’s Donation Payment Gateway.

If Enable Split Donation Payments is not enabled, all Event Items will be assigned to the Event’s (primary) Payment Gateway.

Default Gateways

Users can also use the Payment Gateway's Default Donation Gateway field to select a Payment Gateway record as the default donation gateway.

By setting a Payment Gateway's Default Donation Gateway field to “True” (checked), the Events app will automatically populate the primary and donation Payment Gateways with their respective default gateways when creating an Event. For this to occur, the primary default gateway and the default donation gateway must be linked to the same provider (e.g., Stripe).

When using default gateways, the following will occur if a user enables the Enable Split Donation Payments custom setting and creates an Event.

  • The system automatically populates the Event’s Payment Gateway field with the Payment Gateway marked as the default.
  • If the Donation Payment Gateway field is blank, the system populates the Event’s Donation Payment Gateway field with the Payment Gateway marked as the Default Donation Gateway.

If the Enable Split Donation Payments custom setting is disabled, only the Event's Payment Gateway lookup field is populated with the Payment Gateway record designated as the default.

Event Builder Updates

When creating an Event with the Event Builder, users can add a separate Payment Gateway for a Donation plus the gateway for their Ticket(s).

When the Enable Split Donation Payments custom setting is enabled, users can select a Payment Gateway for a Donation in the Event Item section’s Donation Payment Gateway lookup field.

Only gateways that match the Event’s Payment Gateway will be visible when selecting a gateway in the Donation Payment Gateway field.

If a user creates a new Payment Gateway for the Donation, the Donation Payment Gateway provider must match the Event’s default Payment Gateway provider.

Users will only see the Donation Payment Gateway field after they select the primary Payment Gateway. Once the Event is saved, the Donation Payment Gateway selection will appear in the Event’s Donation Payment Gateway field.

Behind the Scenes

Payment Gateways

The updated checkout method with the Donation Payment Gateway will process multiple Transactions successfully while maintaining support for a single Transaction.

Stripe and Authorize.net

An updated process will generate an encryption key for two-way (symmetric) encryption of credit card data. Encryption keys are stored temporarily and removed immediately after tokenization to minimize unwanted exposure.

The primary and donation Payment Gateways will be tokenized simultaneously with distinct gateway credentials to ensure data security.

Encrypted credit card data will be tokenized. Once the process is complete, the data will be removed from the cache, and the corresponding tokens for each credit card will be used in the checkout process.

Stripe, Authorize.net, and Spreedly

For each registration using a credit card or ACH, a Payment Method will be created in each Payment Gateway and used to process the Transaction in each gateway.

Invoice/Line Item Updates

After all Line Item totals are calculated, users will see a list of all Transactions with separate amounts and gateways.

Event Items with Type = “Donation” will cause the Invoice to include two Line Items – one for the Donation and one for the other Event Item. The related Transaction list on the Invoice will also include two Transactions, each with a different Payment Gateway.

How to Use

Pre-Requisites

  • Your Payment Gateway must be with Stripe or Authorize.net. Currently, no other gateways are supported.
  • ACH Payment Method types are not supported. Attendees can only use card Payment Methods.

Start Here

  1. Check Enable Split Donation Payments in the Blackthorn | Event Settings custom settings.
  2. Create an Event with two Event Items - one “Main event ticket” and one “Donation.”
  3. Set up the primary and donation Payment Gateways.
    1. Add the Payment Gateway for Donations in the Events Donation Payment Gateway field.
    2. Add the Payment Gateway for all other Event Items in the Event Item’s Payment Gateway field.
  4. Set one or more Payment Gateways as the default gateway for each Event Item type.
  5. Complete any additional formatting for your Event.
  6. Publish the Event.

When an Attendee completes the checkout process with at least one “Main event ticket” and one “Donation” ticket, the Event Organizer will see two new Transactions in Salesforce, each processed by the appropriate Payment Gateway.