What is split payment ?
Split payment is a very useful feature when you are working with producers and selling their events for them. The feature will allow to have, at the payment step, a split between the amount of money that goes on the producer account and the amount of money that goes to your account. From Gabelhorn V2, you can have a different merchant at product setup level and point of sales setup level, the ticket price will go to the product merchant id and the fees attached to the point of sales will go to the point of sales merchant id. Let's have a look at the setup and the different possible configuration in more details.
Setup to use split payment
1/ Select the right ePC version compatible with the split payment features Hidden POST 3 (ePC) - V9
2/ add merchant id + SHA key field on product >> tab parameter
3/ add merchant id + SHA key field on point of sales >> tab parameter
How is SecuTix processing the sales with the split payment feature active ?
- Merchant id at point of sales level = merchant id A (corresponds to fees going to the distributor)
- Merchant id at product level = merchant id B (corresponds to the ticket price, fee excluded going to the producer)
- When a payment happens the following rule is processed within the sales engine
- Separate the amount that is a fee (depending on the fee setup of the sales channel) and separate the amount that is the ticket price.
- If there is a merchant id set a at product level then :
- Pay the fee(s) amount to the merchant id A – The total amount (that corresponds to the sum of all fees
- Pay the ticket price amount to the merchant id B
- If there is no merchand id defined a at product level then
- Pay the whole amount to the merchant id A
Fees above correspond to all types of fees (overheads, simple (charges) and shipment fees).
This new configuration opens a lot of possible combinations. Let's dig a bit more into the details of the processing to understand in which cases we have 2 transactions (split payment) and in which cases we have only 1 transaction.
2 transactions are created when the following conditions are met :
- A point of sales AND one or more products have a different merchant id
- AND/OR fees are defined
- AND NOT all products in the order are free
In all other cases, one transaction is created. With one transaction, the money always goes to the ePayment merchant ID.
To get a clearer picture, here is a table summarising some possible combinations
| Description | Split payment (2 transactions) | Result |
|---|---|---|
- Point of sales: merchant A Buy the event (with fees) | NO | Whole amount goes to ePayment merchant ID |
- Point of sales: merchant A Buy the event (no fees) | NO | Whole amount goes to ePayment merchant ID |
- Point of sales: no merchant ID Buy the event (no fees) | NO | Whole amount goes to ePayment merchant ID |
- Point of sales: no merchant ID Buy in the same order event 1 and event 2 (no fees) | YES | Amount of event 1 to merchant C Amount of event 2 to merchant B |
- Point of sales: no merchant ID Buy in the same order event 1 and event 2 (with fees) | NO | Whole amount goes to ePayment merchant ID |
- Point of sales: merchant A Buy in the same order event 1 and event 2 (with fees) | YES | Amount of event 1 to merchant C Amount of event 2 to merchant B Fees to merchant A |
- Point of sales: merchant A Buy in the same order event 1 and event 2 (with fees) | YES | Amount of event 1 to merchant C Amount of Cancel insurance to merchant B Fees to merchant A |
- Point of sales: merchant A Buy event 1 (with fees) | NO | Whole amount goes to ePayment merchant ID |
- Point of sales: merchant A Buy in the same order event 1 and event 2 (with fees) | YES | Nothing to merchant C Amount of event 2 to merchant B Fees to merchant A |
Requirement and Limitations with split payment
- Payment service provider must be Ingenico NPS
- Country Argentina
- All producut Product families are supported
- This feature doesn't work with multiple payment meaning that Vouchers and Promo codes are not supported.
- Refund of split operations cannot be processed from SecuTix. The refund operation must be done in the Payment service provider user interface.
- ePC version Hidden POST 3 (ePC) - V9