Use Cases

You share what you already know. You send Slate your customer's profile and the financial history your platform already has (sales, revenue, orders). No forms, no friction for the customer at this point.

Slate finds who qualifies. Slate underwrites in the background and issues pre-approvals — non-binding offers with an approved amount. You're notified the moment one is ready.

You present the offer. Show it inside your own product: either drop in Slate's ready-made banner component, or build your own UI on top of the offer data. The customer sees financing appear natively in the platform they already use.

The customer applies. One click opens Slate's embedded application. Anything you already provided is pre-filled; the customer confirms details, connects verification if needed, and signs. Slate makes the final decision.

Funds are disbursed, repayment runs on autopilot. On approval, an agreement is created and the money goes out. Slate collects the scheduled installments and keeps you informed of every event — you just reflect the status in your UI.

The customer gets approved for a line. Same start as any Slate product: you share the customer and their financial data, Slate underwrites and approves a credit line application with a maximum facility limit.

You activate the line. You choose the facility limit (up to the approved maximum) and the day its billing calendar starts. From that moment the card is live.

You stream activity in real time. Every swipe, every customer payment, every rebate you fund — you push each one to Slate the moment it happens. Slate keeps the running balance and assigns everything to the right billing period.

Slate bills automatically. At the end of each period, Slate generates an immutable statement with the balance and the minimum payment, and notifies you — you fetch it and show it to your customer. The customer then has a short grace window to pay the minimum.

The line protects itself. If the minimum isn't paid in time, the line is suspended — Slate tells you to block the card, and purchases stop being accepted. Payments keep flowing, and the moment they cover what was missed, the line reactivates on its own and you re-enable the card. No manual intervention on either side.

A worker asks for an advance. Unlike Capital or Credit Lines, there is no offer waiting — the worker initiates. When they request early access to earned wages, you create a finance request in Slate for that exact amount.

The worker confirms in seconds. They complete a short embedded application — most of it pre-filled from what you already provided. First-time users verify identity once; returning users are in and out.

Slate approves and pays out. On approval, the advance is disbursed to the worker. Each request is fully independent: a worker can have several running at once, each with its own status and repayment.

Repayment happens on payday. Slate collects a single repayment — the advanced amount plus a fixed service fee — on the repayment date. You reflect each request's status in your product as the events arrive.