™2 min read
Proxy, don't call direct
Route API calls through your own backend rather than embedding logic in the app, so you can cache, shape payloads and later add authenticated partner calls without shipping secrets in the binary. See proxying.
Hand off in a web view
Submit an enquiry from your backend and open the returned handoff_url in an in-app browser or SFSafariViewController, so the secure application runs on the web where it belongs.
Cache for offline
Cache the product catalogue so the funding screen still renders when the device is briefly offline.
Frequently asked questions
Should the app call the API directly?
Prefer proxying through your backend for caching and future partner calls. Public reads can be called directly if you never need secrets.
How do I run the application flow?
Open the enquiry handoff_url in a web view. The secure application, with identity and consent, runs on the web, not inside your app.
Related reading
Quickstart: Proxy the public API through your backend
A thin backend proxy lets you cache, trim payloads and keep one origin for your front-end — and it is the…
Read →
Quickstart: submit a business-finance enquiry
POST /public/v1/enquiries is how a website or partner hands a lead into Credicorp. Post the company and…
Read →
Quickstart: Cache the product catalogue correctly
The catalogue changes rarely, so caching it removes the API from your hot path and keeps you well under the…
Read →
Quickstart: Keep partner secrets off the client
The single rule that matters when you graduate from public reads to partner writes: a client secret must…
Read →Funding for UK limited companies
Credicorp lends to your company, not to you personally — short-term working capital with no personal guarantee. See what your business could access.