Split Tree

The Split Tree is the set of rules that decides how the money a payment order collects is divided among everyone with a claim on it: the selling merchant, other partner merchants, fee recipients, and Ping itself. It is the machine-readable form of your commercial agreement.

Every payment order carries a Split Tree. While the order is open it just collects funds. When the order is split, Ping evaluates the tree against the funds collected and produces a set of Allocations, the exact amount owed to each party, which are then settled and disbursed.

You don't build it through the API

The Split Tree is not something you construct per order. It is designed once with Ping during onboarding to reflect the agreement between Ping, the tenant, and its merchants, then attached to payment orders. Your integration references it and reads the resulting allocations; it does not author the rules at runtime. The exact internal structure is handled on Ping's side, what you work with is the labelled allocations each split produces.