Architecture Summary

Core shape

Slice is built so product, risk, and reporting concerns stay separated. Publicly, the important shape is:

• the quote path is distinct from the transaction acceptance path,
• reporting reads from recorded evidence rather than recalculating customer terms,
• partner boundaries are carried through quote, transaction, settlement, and payout views,
• private pricing, execution, and infrastructure choices are not part of the public contract.

That separation is what lets a wallet evaluate the integration without needing Slice to publish its operating playbook.

Partner segregation

Pooling and reporting are explicitly partner-scoped. The public boundary is simple: no cross-partner commingling, no custody, and no principal risk shifted onto Slice.

Next step

Return to the API overview or move up to the /technology page for the public diligence view.