Three options
A lender’s API. A bank publishes a programming interface that lets a platform embed lending in its product. For example, Bank CenterCredit describes a Loan API for lending to sole proprietors through partner platforms. This is a market example: we have not checked access terms, and the bank is not a CapVeni partner. Not every bank API includes lending: Halyk Bank’s Open API, for example, describes statements, payments and invoices.
A manual pilot. The platform shows its customers an offer, and applications reach the lender through a link or by hand. Almost no development, but a lot of manual work per application.
Orchestration. An intermediate layer collects consent and data, prepares the application and routes it to a suitable lender among several, by their criteria. The lender still decides, signs the contract and provides the funds. This is not payment orchestration, which routes payments between providers, but routing of financing applications.
Comparing responsibilities, data and effort
A qualitative comparison with no scores or speed claims. Real parameters depend on the specific lenders and contracts.
| Criterion | One lender’s API | Manual pilot | Orchestration |
|---|---|---|---|
| Who builds the integration | The platform, separately with each lender | Almost no development: a link or application handoff | The platform connects to one layer, the orchestrator handles lender connections |
| Products for customers | One lender’s products and criteria | Whatever is agreed for the pilot | Products of several lenders, if they take part |
| Data and consent | As the lender requires, in its process | A manually agreed set, consent recorded by hand | One application format with sources and gaps, consent to share with a specific lender |
| Operational load on the platform | Supporting the integration and customers | High: manual handoff of applications and statuses | Lower for the platform, part of the work sits with the orchestrator |
| Partner dependency | One lender | The lender and manual processes | The orchestrator and participating lenders |
| Decision and credit risk | Lender | Lender | Lender |
| When it fits | A lender has a fitting product and you have integration capacity | You need to test demand quickly on one use case | Customers need different products and one lender is not enough |
Who builds the integration
- One lender’s API
- The platform, separately with each lender
- Manual pilot
- Almost no development: a link or application handoff
- Orchestration
- The platform connects to one layer, the orchestrator handles lender connections
Products for customers
- One lender’s API
- One lender’s products and criteria
- Manual pilot
- Whatever is agreed for the pilot
- Orchestration
- Products of several lenders, if they take part
Data and consent
- One lender’s API
- As the lender requires, in its process
- Manual pilot
- A manually agreed set, consent recorded by hand
- Orchestration
- One application format with sources and gaps, consent to share with a specific lender
Operational load on the platform
- One lender’s API
- Supporting the integration and customers
- Manual pilot
- High: manual handoff of applications and statuses
- Orchestration
- Lower for the platform, part of the work sits with the orchestrator
Partner dependency
- One lender’s API
- One lender
- Manual pilot
- The lender and manual processes
- Orchestration
- The orchestrator and participating lenders
Decision and credit risk
- One lender’s API
- Lender
- Manual pilot
- Lender
- Orchestration
- Lender
When it fits
- One lender’s API
- A lender has a fitting product and you have integration capacity
- Manual pilot
- You need to test demand quickly on one use case
- Orchestration
- Customers need different products and one lender is not enough
Integration does not have to be deep on day one
International embedded-finance providers offer platforms several levels of connection. Parafin, for example, describes a no-code option, a pre-built embeddable component and a custom API integration.
Global programmes are not available everywhere. Stripe Capital lists six countries, and Kazakhstan is not among them. It is worth checking whether a global programme is available before choosing an option.
Data you will need in any option
- Details of the business and its owner, verified by the lender
- Sales or turnover history on the platform
- Order, invoice or purchase data, if financing is tied to a transaction
- Bank statements or open banking data, if the lender requires them
- The owner’s consent to share data with a specific recipient
The National Bank of Kazakhstan is developing open banking in which third parties can access client data only with the client’s consent. Whether specific scenarios are available to intermediaries needs checking at launch.
Sources: 5
Questions to ask before choosing
- Which products do your customers need: working capital, purchases, invoices?
- What data can you share with customer consent, and in what form?
- Who supports the customer when an application is declined or delayed?
- Who is responsible for consent, storage and deletion of data?
- How many lenders do you need at the start, and what happens if a lender changes its criteria?
Where CapVeni fits
CapVeni proposes an orchestration model for platforms and lenders in Kazakhstan. We are preparing our first pilots: the first pilot runs manually, and no lenders or lender API integrations are connected yet.
CapVeni is not a lender and does not issue loans. If one bank’s direct API fits your platform, that can be a sensible choice, and we will say so in the conversation.
Sources
External pages open in a new tab. Banks and providers are cited as market examples, not as CapVeni partners.
- 1.Open API for business (opens in a new tab)Bank CenterCredit · accessed 6 October 2026Describes a Loan API for lending to sole proprietors through partner platforms. Market example, not a CapVeni partner.
- 2.Halyk Open API (opens in a new tab)Halyk Bank · accessed 6 October 2026APIs for statements, payments and invoices between companies. Lending is not described.
- 3.Parafin Capital (opens in a new tab)Parafin · accessed 6 October 2026Integration levels: no-code, pre-built component, API. International example; we have not checked availability in Kazakhstan.
- 4.How Stripe Capital works (opens in a new tab)Stripe · accessed 6 October 2026List of countries where Stripe Capital is available.
- 5.Digital financial infrastructure (in Russian) (opens in a new tab)National Bank of Kazakhstan · accessed 30 September 2026Open banking: access to client data only with the client’s consent.
Prepared by CapVeni from public sources; it describes a proposed model. This is not financial or legal advice. The lender sets the financing terms.