Referral hands the applicant to your flow
In referral mode the applicant is handed over by branded redirect or hosted portal, carrying signed click and lead parameters with UTM and sub-id values passed through, and the application is completed in the flow agreed with you. A server-to-server postback then returns the agreed application or outcome state, so the outcome can be tied back to its click. Partner feedback from postbacks also helps tune the checks over time. Which states come back is agreed during onboarding, for instance submitted, approved, rejected or disbursed. Where the billable event is an agreed partner outcome, that outcome is one of the states the postback reports. The postback guide covers the redirect and the callback in detail.
Direct API delivery posts the application
In API mode a qualified application is posted in real time as structured JSON, using a field map agreed with your team and matched to your schema. Idempotency keys, response handling and retry behaviour are defined before live traffic begins, and status and capacity updates return by webhook. The API guide walks through the request, the responses and the retry rules.
The modes differ in where the application is completed and what you build
Screening works the same way in both modes, so the choice rests on where the application is completed and how much your engineers build.
| Dimension | Referral and postback | Direct API |
|---|---|---|
| Where the application is completed | The applicant is handed over by branded redirect or hosted portal, and the application is completed in the flow agreed with you. | Your endpoint receives the qualified application as JSON, mapped to your schema. The credit decision and any steps you require before it stay with you. |
| What you receive | The applicant, arriving with signed click and lead parameters, with UTM and sub-id values passed through. The application record is created in that flow. | A structured JSON application in real time, mapped to your schema through the agreed field map. |
| What your team builds | Entry handling that checks the signature and stores the click ID with the application, plus a postback call to us on each agreed outcome. | An endpoint that validates the payload, honours idempotency keys and returns clear status codes, plus handling for the webhooks that carry status and capacity updates. |
| Best fit | Lenders with a working application flow and limited engineering time, who want attribution and feedback without building a new endpoint. | Lenders with a decision system and engineering capacity, who want applications to enter it directly with no re-keying. |
Four questions decide which mode fits
The questions are about your own systems and team, because screening and commercial terms are the same in both modes. Answer them before the first conversation.
| Question | Points to referral | Points to direct API |
|---|---|---|
| Does an application flow already exist? | Yes. You run a flow that completes the application, and applicants can be handed to it. | No flow to hand applicants to, or you want applications to enter your decision system directly. |
| Is an engineer available for a new endpoint? | Engineering time is limited. The build is entry handling and a postback call. | Yes. The endpoint, idempotency handling and webhook handling are engineering work. |
| Who stores the click ID? | Your side, with the application, and it comes back to us in the postback. | Only if the agreed field map includes it. The field map decides which identifiers travel in the payload. |
| Who owns retries and duplicates? | Your server sends the postbacks, so you own their retries and the duplicate rule agreed with us. | We send each request with an idempotency key and retry under the agreed rules. Your endpoint answers a duplicate consistently. |
Each side owns different parts of the handoff
| Area | CYBERTECH | Your team |
|---|---|---|
| Criteria and capacity | Screens applicants against your rules before any handoff, in both modes. | Defines the market, the product criteria and the capacity. |
| Credit decision | Not a lender, so no part in the decision. | The final decision, and any steps you require before it. |
| Click ID | Passes it to you on the redirect in referral mode and records the outcome returned against it. | Stores it with the application and returns it in the postback. In API mode, carries it if the agreed field map includes it. |
| Retries and duplicates | In API mode, retries failed requests under the agreed rules, reusing the idempotency key. | Answers a duplicate API request consistently. In referral mode, retries postbacks and applies the agreed duplicate rule. |
| Before go-live | Agrees the parameters or the field mapping with you. Provides the sandbox environment and API keys in API mode. | Agrees the same, and names a technical and an operational contact. |
Screening, pricing and markets do not depend on the mode
In both modes you define the market, the product criteria and the capacity. Applicants are screened against those rules with five checks: device integrity, network, identity, behaviour and velocity, and fit to your criteria. Signals are read together, so no single check decides. Only suitable applicants are routed to you, and you keep the final credit decision.
Commercial terms follow the same shape in both modes: CPA on a qualified application or an agreed partner outcome, or CPD on a disbursed loan, with the billable event defined together before launch. Daily or monthly caps apply per market and product, and delivery is throttled when a cap is reached. Pricing explains the billable events.
Supply varies by market and product, and each launch is confirmed market by market: India, Kazakhstan, Armenia, Nigeria and Peru.
Identifiers, retries and duplicates are settled before go-live
In referral mode, signed click and lead parameters travel on the redirect with UTM and sub-id values passed through, and the postback returns the click ID with the outcome, so each outcome joins to its click, source and campaign. In API mode, the field map agreed with your team decides which of these fields travel in the payload. The postback guide lists the illustrative parameters and explains how to verify them and what to keep out of URLs.
Retries and duplicates are agreed just as early: which failures are retried, how many attempts are made and which response a duplicate receives. An idempotency key lets a receiver recognise a retried API request, and the API guide covers it in detail. The postback guide does the same for duplicate and late postbacks.
Launch follows the same sequence in both modes
Live routing starts only at go-live. The steps before it settle what is delivered and how.
- Criteria and capacityAgree the criteria and the capacity per market and product, with the caps and the billable event set at the same time. Your team keeps the final credit decision.
- Parameters or field mappingFor referral, agree the parameter list, what the signature covers and the postback URL. For the API, agree the full field mapping to your schema, the idempotency-key rules and the error responses.
- Sandbox and pre-launch checksThe API mode comes with a sandbox environment and API keys, so both teams can exercise validation and error responses with test payloads before go-live. For referral, the parameters and postback setup are agreed before launch.
- Go-liveLive routing starts once the field mapping and operational contacts are confirmed. Each launch is confirmed market by market.
With traffic live, the postback returns the agreed outcome states in referral mode, and webhooks carry status and capacity updates in API mode.
Bring the following to the first conversation:
- The market and product you want to open, and the criteria an applicant must meet.
- Daily or monthly capacity, and what should happen when it is reached.
- Whether the application lives in a flow you already run or in a decision system with an API.
- A technical contact for the field mapping and an operational contact for go-live.
Postback and API guides cover the details
- Implement a referral redirect and S2S postback for loan leadsHow to store redirect parameters, verify the signature, send outcome statuses and handle retries and duplicates.
- Receive loan leads by direct API with idempotent requestsLenders' engineers map fields, handle idempotency keys, retries and webhooks, and test in a sandbox before applications go live.
Related guides
- How CPL, CPA and CPD price loan leadsHow CPL, CPA and CPD differ on risk and reporting, and which terms to fix in writing: billable event, validation window, caps.
- Screen loan leads for fraud and fit before they reach youFive checks, including fit to your own criteria, screen applicants before handoff. No single signal decides, and a stopped applicant is not delivered to you.
- Lending acquisition glossary, from CPA and CPD to DLG and DPDDefinitions of lending acquisition terms, from CPA, CPD and postbacks to NBFC, LSP, DLG, MFO and loan stacking, with links to the guides that go further.