LOADING
MERCHANT AND CUSTOMER SERVICE
One timeline per relationship. Sales activity, application progress, documents, underwriting messages, support tickets and disputes, in the order they happened.
Leads through live processing, with attribution, next actions, expected volume and residuals. Agents see stage progress, not merchant files.
Email, SMS, calls and notes attach to the merchant rather than living in someone's inbox. The timeline is the account history.
Orders, payments, shipping, documents, disputes and buyer eligibility state — enough to resolve a case without switching systems, and without exposing raw identity documents.
Transaction, order, buyer verification, attestation version, delivery and communications assemble into a representment packet on request.
Sourced or inbound, attributed to an agent permanently from the referral link forward.
Sent, started and completed, with stage progress visible to the agent throughout.
Email, SMS, calls, notes, documents and underwriting messages land on one record in the order they happened.
On activation the relationship moves to merchant service without losing the history that preceded it.
Tickets carry the whole customer record — orders, payments, shipping, documents, eligibility state.
Transaction, buyer verification, attestation version, delivery and communications assemble into a representment packet.
Calculated on settled volume, netted for chargebacks and refunds in the period they post.
An agent sees pipeline stage and never a compliance finding. A support representative sees buyer verification state and never the underlying ID. Row-level isolation enforces this in the database, not in the interface.
A named contact assigned at activation rather than a queue, with the ticket history attached to the account.
