Versions Compared

Old Version 2

changes.mady.by.user MMI

Saved on

compared with

New Version Current

changes.mady.by.user Ian RICKEBUSCH

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
TODO

What is

Split

split payment ?

Requirement to use split payment

Payment provider must be Ingenico NPS

Country Colombia + Argentina

Product families all supported ?

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

The operator would be able to do the following setup

1/ Select the right ePC version with the split payment features Hidden POST 3 (ePC) - V9

Image Added

2/ add merchant id + SHA key field on product >> tab parameter

Image Added

















3/ add merchant id + SHA key field on point of sales >> tab parameter

Image Added

How is SecuTix

is

processing

your

the sales

How the system will process the sales in such cases

Set a merchant id + SHA key 

with the split payment feature active ?

  1. Merchant id at point of sales level = merchant id A (corresponds to fees described below going to the distributor) => in our case, will be tuboleta etc…Set a merchant id + SHA key
  2. Merchant id at product level = merchant id B (corresponds to the ticket price, fee excluded going to the producer)
  3. When a transaction is happening payment happens the following rule is processed within the sales engine
    1. 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.
    2. If there is a merchant id set
a
    1. at product level then :
      create a sub operation to pay
          1. Pay the fee(s) amount to the merchant id A  –
      this sub-operation is the
          1. The total amount (that corresponds to the sum of all fees
      )create a sub operation to pay
          2. Pay the ticket price amount to the merchant id B
        2. If there is no merchand id defined
      a
        1. at product level then
      :
          pay
              1. Pay the whole amount
          on
              1. to the merchant id A

          Notes:

          1/ fee = 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

          What about fees ?
          DescriptionSplit payment (2 transactions)Result

          - Point of sales: merchant A
          - Event: no merchant ID

          Buy the event (with fees)

          		NOWhole amount goes to ePayment merchant ID

          - Point of sales: merchant A
          - Event: merchant B

          Buy the event (no fees)

          		NOWhole amount goes to ePayment merchant ID

          - Point of sales: no merchant ID
          - Event: merchant C

          Buy the event (no fees)

          		NOWhole amount goes to ePayment merchant ID

          - Point of sales: no merchant ID
          - Event 1: merchant C
          - Event 2: merchant B

      Some example

      Buy in the same order event 1 and event 2 (no fees)

      		YESAmount of event 1 to merchant C
      Amount of event 2 to merchant B

      - Point of sales: no merchant ID
      - Event 1: merchant C
      - Event 2: merchant B
      - Some kind of fees

      Buy in the same order event 1 and event 2 (with fees)

      		NOWhole amount goes to ePayment merchant ID

      - Point of sales: merchant A
      - Event 1: merchant C
      - Event 2: merchant B
      - Some kind of fees

      Buy in the same order event 1 and event 2 (with fees)

      		YESAmount of event 1 to merchant C
      Amount of event 2 to merchant B
      Fees to merchant A

      - Point of sales: merchant A
      - Event 1: merchant C
      - Cancel insurance: merchant B
      - Some kind of fees

      Buy in the same order event 1 and event 2 (with fees)

      		YESAmount of event 1 to merchant C
      Amount of Cancel insurance to merchant B
      Fees to merchant A

      - Point of sales: merchant A
      - Event 1: merchant C - free event (price 0)
      - Some kind of fees

      Buy event 1 (with fees)

      		NOWhole amount goes to ePayment merchant ID

      - Point of sales: merchant A
      - Event 1: merchant C - free event (price 0)
      - Event 2: merchant B - price >0
      - Some kind of fees

      Buy in the same order event 1 and event 2 (with fees)

      		YESNothing 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