Step 1 — Two brands, one workspace
Create Brand A and Brand B under the agency. Leads and orders are stored on the brand they belong to — a tag named “Brand B” in a shared list is not this split.
Isolated brand pipelinesHere’s how this workflow can be configured in Ledrix when two client brands must collect on different Stripe or PayPal accounts. This is an example scenario, not a result a customer reported.
Keys are saved on the brand first. Ledrix does not auto-split a shared agency Stripe.
Agency founder or ops who mixed merchants
Consider an agency running Client Brand A and Client Brand B with the same sales team. Brand A must collect on its Stripe account. Brand B must collect on its PayPal (or a second Stripe). A shared agency default is the failure mode.
Order card: Send payment link, with that brand’s Stripe or PayPal — not a shared default.
Create Brand A and Brand B under the agency. Leads and orders are stored on the brand they belong to — a tag named “Brand B” in a shared list is not this split.
Isolated brand pipelinesOpen the brand and paste that client’s Stripe or PayPal keys. Ledrix does not auto-discover merchant accounts. If Brand B has no keys, you cannot honestly send Brand B’s money to Brand B.
Per-brand merchant keysWhen the buyer says yes, generate Stripe or PayPal from the lead or order. The link is created under the merchant saved on that brand. You do not hop to a shared billing tab and guess which login to use.
Payment links from the dealWebhook events attach to the payment that was taken. A dispute is not a Slack hunt for “which client was that?” Eligible plans include chargeback tracking on that payment.
Payment events on the right record14-day free trial, no credit card. Sandbox is shared sample data — a trial is your own workspace.
Straight answers about how Ledrix is configured — not claimed customer results.