Skip to main content

Banking and money movement

Use this path when finance teams work in your ERP, CRM, accounting product or operations platform and need Hubpay account information without leaving that system.

This area covers the APIs commonly described as embedded banking, bank feeds, treasury integration or payment initiation.

What you can build​

  • Multi-currency wallet balances
  • Transaction feeds for reconciliation and reporting
  • Beneficiary management
  • Payment quotes and payment initiation
  • Event-driven updates through signed webhooks

Typical flow​

  1. Your backend authenticates with Hubpay using client credentials
  2. Map the customer or organisation in your product to its Hubpay AccountId
  3. Read balances and transactions into your product
  4. Create beneficiaries, quotes and payments from an authorised server-side workflow
  5. Use webhooks to keep payment and transaction state current

Salesforce integrations​

For a Salesforce implementation, keep Hubpay credentials and API calls on the server side:

  • Use a Salesforce External Credential and Named Credential for the Hubpay endpoint and authentication material
  • Use a named principal when one approved service identity acts for the Salesforce organisation
  • Map Salesforce account records to the relevant Hubpay AccountId
  • Make callouts from Apex, External Services or middleware rather than browser code
  • Send Hubpay webhook events through your integration layer and update Salesforce records asynchronously

Salesforce recommends its current extensible Named Credentials and External Credentials model instead of legacy named credentials.

SSO and API access are separate​

Client credentials authenticate your server to the Hubpay API. They do not sign a Salesforce user into Hubpay.

If users need to open Hubpay from Salesforce without another login, treat that as an enterprise SSO requirement using an agreed identity federation protocol such as OIDC or SAML. Confirm the tenant and identity-provider setup with Hubpay before implementation.

When to use connected apps instead​

Use this bank-feed model when a business is integrating its own Hubpay account into its own systems.

If you provide a multi-tenant software product to many independent Hubpay customers, use Connected apps so every customer approves and controls access to their own account. Do not distribute one customer's API credentials through a shared application.

Start here​