Credit Core
Credit Core (Credits API v2) is Migo's foundational credit product. A third party consumes it to build its own credit or lending solution without integrating with each financial institution separately: Migo coordinates bank affiliation, account lookup and the full credit transaction lifecycle through a stable contract.
The idea is simple: you call a single API and Migo handles talking to each financial institution (BAM, GE or another). If a new bank is added tomorrow, your integration doesn't change β the bank travels as one more value in the URL (bankSlug) and every response always has the same { success, data } shape.
It is meant for third parties β merchants, fintechs or platforms β that want to offer credit to their users without building and integrating with each bank separately. You don't need to know Migo's internal infrastructure: the endpoints in this section are enough.
In 6 stepsβ
The happy path, end to end, is six calls: you create the user, affiliate them to a bank, validate the OTP the bank sends them, create the transaction, authorize it (the bank reserves the amount) and capture it (the charge runs). Each step is explained, with its real example, in the Overview.
What you can buildβ
- A credit onboarding flow: create the user, affiliate them to a financial institution and validate the OTP.
- A buy-on-credit flow: create the transaction, preauthorize the amount and capture the charge.
- A pre-qualified flow: register pre-approved users before completing bank onboarding.
- An account lookup panel: balance, approved amount, used amount and upcoming payments.
- Voids and cancellations, including automatic cancellation on expiration.
API areasβ
Each area groups a set of endpoints under a URL prefix:
| Area | Prefix | What it's for |
|---|---|---|
| Users | v2/credits/users | Create users, affiliate them to a bank, OTP, pre-qualifieds |
| Transactions | v2/credits/transactions | Create, authorize, capture, cancel and void |
| Accounts | v2/credits/accounts | Look up an account's balance/limit and send its OTP |
| Webhooks | v2/credits/webhooks | Notices the bank and other systems send to Migo |
Integration pathβ
- Overview β how it fits together and the end-to-end flow with examples
- Authentication β how you identify yourself and what responses look like
- Users and pre-qualifieds β create/query users and register pre-qualifieds
- Bank affiliation and OTP β associate the user with a financial institution
- Account lookup β account data and account OTP
- Transaction lifecycle β new β authorize β capture β cancel/void
- Webhooks and notifications β the notices you receive from the bank and collector
- Error catalog β what each code means and when to retry
For exhaustive technical detail of schemas, fields and status codes, browse the live Credit Core interactive reference.