Introduction

Merchants often have multiple revenue streams. In these cases, the partner split payment method can become a constraint, as payments can only be collected from the portion of revenue flowing through your platform. This limits the size of the offers Liberis can provide.

Bank Debit (direct debit) is used when a merchant generates significant revenue outside of your platform and a partner split would not capture enough funds to be viable. Because bank debit is handled entirely by Liberis, there are no implementation steps required from you as the payment processor.

Fallback Partner Split

The exception to the above is if we are unable to collect satisfactory payments via bank debit. In such cases, we may have agreed with you to use partner split as a fallback payment method. While this is undesirable because it again limits collection to a portion of the merchant's total revenue, it ensures we can recover some funds when bank debit has been ineffective.

When used as a fallback for bank debit, partner split works identically to when it is the primary payment method. For detailed instructions, refer to Implementing Partner Split. Liberis handles de-duplication between bank debit and partner split to ensure the merchant is not split twice for the same revenue — ensure that you are regularly and accurately recording partner split payment information to the Settlement API.

Partner split creation will be requested on-demand, per-merchant, at the point it becomes required. This is why it is critically important not to couple your partner split implementation, via the Payment Processor API, to the statuses (or status changes) of specific advances from other endpoints in the Capital Platform API.

We do not attempt partner split setup in advance of it being required, i.e. we do not send partner split actionRequired webhooks pre-emptively.