Skip to main content
Credit rules differ by market. Rather than hard-code one country’s rules, Lender is jurisdiction-aware: it carries a registry of jurisdiction profiles, each supplying the rules, disclosures, and calendar its market needs, and the active jurisdiction shapes which behavior applies.

​
The profile model

  • Generic — a baseline profile with the market-neutral lending behavior every jurisdiction shares. It is the fallback when no country-specific profile applies.
  • Brazil (BR) — a deep profile layered on top of the baseline, adding CET disclosure, IOF preview, capitalization consent, PDD staging, the credit-operation descriptor, prepayment quotes, a Brazilian business calendar, and the consignado privado journey.
Brazilian behavior is reached through BR-prefixed endpoints (/api/v1/br/...), several of which are jurisdiction-aware aliases of the generic operations. See the Brazil regulatory pack and Consignado privado.

​
Discovery endpoints

The compiled-in profiles are discoverable at runtime, so a client can learn which jurisdictions a deployment supports:
OperationPurpose
GET /api/v1/jurisdictionsList the registered jurisdiction profiles.
GET /api/v1/jurisdictions/{code}Read one jurisdiction profile by its code.
Profiles are part of the deployed service, not runtime configuration — discovery tells you what a given deployment can do, not something you edit through the API.

​
Next steps

Brazil regulatory pack

Everything the Brazilian profile adds.