API and Integration Model
Bansoft provides a documented SOAP web services layer for controlled inbound and outbound integrations. Methods, credentials, environments, and third-party dependencies are scoped according to institutional requirements.
How does the Bansoft integration layer work?
Documented integrations use SOAP web services with XML communication over HTTPS and controlled access to approved methods.
API credentials
External API keys can be issued for an approved integrator, restricted by IP, associated with permitted methods, and aligned with the administrator permission model.
Method-level scope
The documented API covers user profiles, accounts, balances, transactions, transfers, documents, and compliance-related functions. Only the required methods should be enabled.
Secure communication
Requests and responses use XML over HTTPS. Validation, response codes, permissions, and audit logging support controlled integration behavior.
Approved methods are confirmed during technical review
Documented categories include user creation and profile updates, account creation and balances, debit and credit transactions, transfers between users, document uploads, and KYC-related data access.
The available methods, versions, parameters, and response codes must be confirmed against the current integration documentation and enabled scope.
Access should match the integration need
- Unique API key per integrator
- Restricted source IPs where required
- Method permissions aligned to role
- Audit logging of API activity
- Credential rotation and revocation procedures
Illustrative onboarding and transaction flow
The exact flow depends on the partner, integration, and institution's approval rules.
- Commercial and technical onboarding: confirm partner scope, branding, environment, and trusted network details.
- Credential setup: issue an API key and permit only approved methods.
- Create or update a profile: submit required customer and KYC data and receive the Bansoft user identifier.
- Create accounts: open one or more accounts according to configured account types and currencies.
- Submit a funding or transaction request: use an enabled transaction method and follow the institution's validation workflow.
- Review or execute: process automatically or route to an administrator queue according to configuration.
- Update balances and logs: post the transaction, update account data, and record the activity.
- Refresh the partner experience: poll approved methods or use available eventing options where configured.
Integration environments are scope-dependent
Sandbox or development environments may be provided for evaluation, testing, training, and integration work. Endpoints, credentials, data handling, and restrictions are confirmed when the environment is provisioned.
Integration support is not the third-party service
Bansoft can connect with approved external systems, but payment rails, identity services, screening providers, market data, and other third-party services remain separate and may require their own contracts, fees, controls, and regulatory review.
Core banking connected to separately scoped payment services
Bansoft can be evaluated as the managed core banking layer alongside approved payment infrastructure providers. Account and transaction records remain within the agreed platform scope; payment messaging, clearing, settlement, network access, and provider services require separate technical and commercial review.
Provider onboarding, credentials, transaction controls, reconciliation, fees, and operating responsibilities must be agreed before implementation. Integration capability is not a promise that a particular payment network or provider is included.
Related Bansoft resources
Continue with the most relevant product, service, and evaluation information.
