12 docs tagged with "api"

Endpoints available to validate and populate info regarding Bic Codes, Routing Numbers and IBANs

Connect Financial offers a range of card programs designed to cater to diverse user needs. These programs encompass both virtual and physical cards, providing flexibility and convenience.

Below is a log of changes to the Connect Financial API. Updates that affect only products or features in beta or limited release may not be reflected.

Our KYC flow entails inputing the required information withing a customer record, starting the process with a specific api call in this category, redirecting the customer to a link or qr code given withing this call (depending on your negotiated KYC strategy) and uploading the missing documents.

Each customer is an end-user created under a client account. Customers can be either individual customers or businesses.

To deposit digital assets like Bitcoin to wallets, it's necessary to generate a digital asset address beforehand. And once there is crypto withing a wallet the dedicated withdrawal endpoint needs to be used to transfer it out of the wallet.

In sandbox, we may want to force some scenerios for testing purposes, and simulate some operations like deposits. This category of endpoints is only available on sandbox.

Trade quote generation and execution for B2B trading operations.

Generate JWT tokens for Vault SDK integration.

In our system, accounts refer specifically to Virtual Accounts, which allow users to send and receive fiat currency using standard banking rails like ACH, FedWire, and SWIFT. These are distinct from wallets, which hold the actual asset balance.

Wallets serve as the core value-holding accounts in our B2B API ecosystem.

Some operations in our system, like deposits, occur asynchronously. To receive notifications about this operations you'll need to subscribe to it by registering a webhook to it's respective event.