Add a merchant or a market without shipping code
Your decision happens inside somebody else’s checkout, at their traffic, with their latency budget. It has to answer fast, answer consistently, and answer the right question: which financing this customer can actually be offered here.
Eligibilityrules
Per-merchantpolicy
Instantscoring
Regionalendpoints
The decision behind the button
Eligibility in embedded finance is rarely one rule. It is a set of constraints that have to be resolved together, in one call.
Which financing applies
Cross-check the customer, the basket, the merchant, the market and the product catalogue in one decision, instead of hard-coding eligibility across integrations.
Per-merchant and per-market rules
The same platform, different constraints by merchant, segment and jurisdiction, without forking the logic or shipping a variant per partner.
Instant credit and affordability
Scoring, affordability and fraud signals resolved inside the flow, with external lookups running in parallel so latency is bounded by the slowest call, not their sum.
Consistency across channels
The eligibility answer at checkout and the one in the partner portal come from the same decision flow, so they cannot disagree.
Real time, and almost only real time
This is the most latency-sensitive thing we do, and the surface that matters is instant decisioning.
- Real-time endpoints, in your region. One REST call from the partner integration, answered in milliseconds through real-time decisioning.
- Parallel lookups with fallbacks. Bureau, fraud and device calls run together inside the flow, with the timeouts and fallbacks you set - a slow provider degrades the decision, it does not hang the checkout.
- Change the rules without a partner release. Eligibility changes ship as a release on your side, not as a code change in every integration.
Someone still has to answer for the decision
Distribution through a partner does not move the obligation. Where the underlying product is consumer credit, creditworthiness assessment falls under the AI Act Annex III provisions from 2 December 2027, and GDPR Article 22 applies to the decline today. The trace has to exist even when the customer never saw your brand.
Questions we get asked
What latency should we expect?
Milliseconds for the rules and models. Real-world latency is dominated by external data calls, which is why they run in parallel inside the flow with timeouts you control.
Can eligibility differ per merchant and per market?
Yes, and that is the normal case. Merchant, market, segment and product constraints resolve together in one decision rather than being scattered across integrations.
What happens when a data provider is slow or down?
You define the timeout and the fallback. The decision degrades in the way you specified instead of failing or hanging.
How do we roll out a rule change across partners?
As a release on your side. Partners keep calling the same endpoint; the logic behind it moves through your approval process.
Do we need case work for this?
Usually not. Embedded finance decisions answer in one request. If you also run disputes or chargeback investigations, those are the ones that belong in case work.