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

​
The profile model

  • Generic (XX): the base profile. It books no credit: Lender refuses to create a product, a version, or an application under it. A tenant with no jurisdiction binding is refused with 403.
  • Brazil (BR): the profile that books credit. It adds CET disclosure, IOF preview, capitalization consent, PDD staging, the credit-operation descriptor, prepayment quotes, a Brazilian business calendar, and the consignado privado journey.
You reach Brazilian behavior through BR-prefixed endpoints (/api/v1/br/...). Several of those endpoints 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:
Profiles ship with the service, not as 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.