Skip to main content
Kashimi supports two integration approaches. The difference comes down to one question: who shows the bank selection screen to the PSU?

Custom Bank Selection

Custom Bank SelectionYou fetch the list of banks and render your own bank picker inside your UI. The PSU selects a bank without ever leaving your application. You pass the selected provider.id when initiating the payment.Best for: teams that want full control over the checkout experience and brand consistency.

Hosted Bank Selection

Hosted Bank SelectionYou skip the bank list entirely. Kashimi redirects the PSU to its own hosted bank selection screen, where they pick their bank and authorise the payment. No provider.id required.Best for: teams that want the fastest integration with minimal frontend work.

Comparison

Custom Bank SelectionHosted Bank Selection
Bank selection UIBuilt by youKashimi hosted screen
Time to integrateLongerFaster
Brand & design controlFull controlLimited
Bank list maintenanceYou manageAutomatic
provider.id requiredYesNo
PSU leaves your appNo (until bank redirect)Yes (to Kashimi screen first)

Which should I choose?

Custom Bank Selection

Full brand and design control
Seamless experience — PSU never leaves your app before bank redirect
Custom bank filtering, ranking and search
Works well in native mobile apps

Hosted Bank Selection

Pre-built bank selection UI — no frontend work
Quick to implement — 1 API call
Kashimi keeps the bank list updated automatically
Real-time webhook notifications for payment status
Both flows go through the same redirect step to the bank’s website for PSU authentication and payment approval. The only difference is who renders the bank picker before that redirect happens.