Ways to connect
Email only, API with white-label completion, or API with your own journey, and what each one costs you to run.
Three levels, told by what you build. Every level feeds the same marketplace, so the applicant compares your terms next to the rest of the panel. Pick the one your team can run without starting a project.
Level 1. No build
We send each routed deal to your intake inbox with the figures, the register facts and the statements attached. You reply with your decision or your terms. Statuses come back from a structured reply or from a private inbound link we give you, and land in the same pipeline as an API status.
| What you build | nothing |
|---|---|
| Time to live | a day |
| What you give up | no push events, no offer comparison in the client view until we key your reply in |
Full detail, including what the referral email carries and what changes once statements arrive: Deals by email.
Level 2. API, white label
The client never leaves the brand they applied through and meets your name on the agreement. You receive the complete deal by push, post an indicative offer, then a firm offer once statements are in, and upload your funding agreement as a PDF. The client confirms the payout account and signs on the marketplace, and both moments reach you as events.
| What you build | an endpoint that accepts our push, and calls for offers and the agreement |
|---|---|
| Time to live | days |
| What you get | no customer journey to design, host or maintain, and the shortest path from routed to signed |
Level 3. API, your journey
Identical to level 2 up to acceptance. Then you attach your continuation link to your accepted offer and the client finishes in your product, on your screens, under your terms of business.
| What you build | everything in level 2 plus the journey the client lands in |
|---|---|
| Time to live | as long as that journey takes |
| What you get | full control of the close out |
Side by side
| No build | API, white label | API, your journey | |
|---|---|---|---|
| Deal reaches you | Push, full deal object | Push, full deal object | |
| Offers | In your reply | Indicative, then firm | Indicative, then firm |
| Statements | Attached | Signed links on the event | Signed links on the event |
| Agreement | Yours, outside | Your PDF, signed with us | Yours, in your journey |
| Payout account | You collect it | We collect, you read it | You collect it |
| Client sees | Your emails | One brand, your name on the document | Your product after acceptance |
| You build | Nothing | One endpoint and three calls | That plus a journey |
Or we build yours
If you already expose an onboarding API that accepts applications and returns indicative offers, we build and maintain the adapter and post into it. That is how several lanes on the panel run today. Nothing is built on your side beyond giving us the schema, a sandbox key, the per-country required fields and the status callback.
Mixing levels
Levels are per lane, not per company, and they are not a one way door. Start on email, move to push when it pays, add the agreement step later. A status reported by API, by the private inbound link or by a structured email reply all land in the same pipeline, so history stays in one place.