Skip to content
New guide — how platforms turn payment data into a capital programRead it →

Every screen yours. Every hard part still ours.

Build the entire financing experience yourself against a REST API and signed webhooks. Slate still carries the underwriting, the money, the compliance and the collections.

POST /v2/customers
x-api-key: "…"
{ "externalId": "acct_8812" }

Webhooks back

offer.createdOffer issued
application.approvedApproved
credit-line.draw.fundedMoney out
payment.receivedRepaid

Every meaningful event arrives signed. You never poll.

Total control of the surface.
None of the risk underneath.

You design and ship every screen. Underwriting, money movement, compliance and collections stay entirely on Slate's side of the line.

Nothing decided for you

Every screen, every state, every word is yours to design. No component dictates the interface.

Events, not polling

Offers issued, applications approved, money out, payments received — each arrives as a signed webhook.

The operating model is unchanged

Building the UI yourself does not move underwriting, compliance or collections onto your side.

What your team actually does

01

Authenticate and register

Take an API key from the sandbox dashboard and create each customer against your own stable identifier.

02

Share the financial data

Send the history your platform already has. Fresher data means better offers for your customers.

03

Listen and render

Subscribe to the webhooks, react in your own UI, and ship exactly the experience you designed.

Pick this if

Financing is a first-class part of your product, not a bolt-on

You have design and engineering capacity to own the surface

You need custom states, custom copy or an unusual flow

You want the deepest integration available

Look at another path if

You want to prove demand before committing engineering time.

Ready to launch

You want your own layout, but not the lending logic.

Drop-in components

Own the experience. Not the risk.