What is prepared before API calls start?
A business client is activated for the product, allowed services are configured, and signing keys are exchanged so Gateway can trust every request.
Banking integration demo
Banking services for your business clients
HashBank helps businesses offer banking journeys through their own digital channels. This demo shows how customer onboarding, accounts, cards, and corporate operations work from start to finish.
How it works
Choose a scenario and see what happens
The page works like a guided help center: choose the flow you need, run it step by step, and see the business result together with the signed technical details.
Setup
Customer
Banking
Security
How does a customer become eligible?
The customer accepts terms, a profile is created, documents are uploaded, and KYC is completed before accounts or cards are opened.
What can the business test after verification?
The demo opens accounts, issues cards, shows secure card-data access, and tests card actions such as block, unblock, close, and PIN operations.
Embedded customer banking
Use this path when a business client wants to provide HashBank services to its end customers inside its own app or platform. It shows resident and non-resident journeys.
- Customer accepts terms and is registered
- Identity and KYC are completed
- Account, card, and card controls become available
Corporate account and card banking
Use this path when a business client connects its own back office, treasury, or employee-card processes directly to HashBank corporate APIs.
- Company authorization is confirmed
- Accounts, cards, and transactions are retrieved
- Card actions are tested with audit-ready requests
Security built in
Every call is signed. Every result can be verified.
Gateway requests use RFC 9421 HTTP Message Signatures. The demo shows what was sent, what was returned, and whether the response signature was verified.
Request signed with partner key
Gateway validates access and service permissions
Response is verified with HashBank platform key