Developer Overview
Learn how to integrate with Branch
This guide is designed to help your organization seamlessly integrate with Branch's infrastructure for fast, flexible worker payments.
Through this guide, you’ll explore the full journey—from initial evaluation and solution selection to system design and implementation—enabling you to deliver reliable payouts to your workforce. From start to finish, we provide the tools and support to simplify every step of the process.
Have solution documentation from Branch? If your Branch team gave you a Solution Overview or implementation plan, follow it. It's written for your integration and takes precedence over the standard paths on this page.
Start using the Branch API
Before using the Branch API, make sure you’ve connected with the Branch Sales Team so that you’re set up with the right solution for your organization: [email protected] or (800) 219-7212 (Press 1 for Sales).
Once you’ve had a kickoff call with Branch and your organization’s key business and technical stakeholders, the Branch team will provide an API key for the sandbox environment. Follow the API Reference guide to learn how you can use the sandbox API key to try the Branch API.
Choose your solution
Branch offers several solutions, and they don't all integrate the same way. The webhook that tells you a worker is ready, and the way money moves, depend on the solution.
If your organization pays its workers (wages, tips, gig earnings) instantly to a Branch Wallet or their own debit card, follow the onboarding and payment steps on this page. This includes Disbursements with Tax Filing, Co-Branded Card, or Whitelabel; branding is configured with Branch during implementation.
For other Branch solutions, your Branch team provides the integration documentation.
Begin worker onboarding
Branch offers multiple solutions to onboard workers. Onboarding a Worker authorizes and enables them to receive digital payments from your organization sent via Branch.
Authenticating workers links a WorkerID to a Branch account, which is claimed when the worker verifies matching contact information using a One-Time Password. The worker provides information for creating or linking a payment method, according to the system your organization implements for configuring worker payment methods. The organization activates worker payments upon confirmation of successful payment method configuration.
The configuration your organization chooses to develop for worker payment methods will impact how authenticating workers and activating worker payments are implemented.
| Name | Description | Considerations |
|---|---|---|
| Standard Web Portal Recommended | Customer embeds Branch widget or redirects to web browser. | Lightweight build and ongoing maintenance. Branch manages all screens for onboarding, payment history, and payment profile updates. |
| Embedded API | Customer builds to Branch APIs | Existing integrations only; not a standard path for new integrations. Customer manages screens for onboarding, terms acceptance, payment history, and payment profile updates. |
Standard Onboarding Paths
| Name | Process |
|---|---|
| Wallet Only |
|
| Wallet + Branch Direct |
|
Embedded API Onboarding Paths
Some existing integrations use these paths, where the organization sends KYC data to Branch. They aren't part of the standard path for new integrations. Use them only if your Branch solution documentation specifies them.
| Name | Process |
|---|---|
| Wallet + Branch Direct |
|
Receive events from Branch using Webhooks
Follow the Webhook Implementation guide for a start-to-finish checklist and visualization of the Webhook system components. Using Webhooks for reacting to payment profile activation is required to ensure workers are eligible for payouts. Don't pay a worker until the PAYMENT_PROFILE_ACTIVATED webhook arrives.
Pay Workers
Branch is able to provide payments to your organization's workers quickly without a fee, no pre-funding required. Enabling this feature requires your organization to provide funding sources for Branch to invoice the repayment of these disbursements using ACH. Use Create Disbursement (V2).
Close Worker Accounts
Worker accounts can be closed for a variety of reasons, triggering events which prevent their payment eligibility. Follow the Wallet Closure guide for more details.
Find relevant documentation
Each guide for the important features listed on this page contains links to detailed implementation techniques. These guides are also visible on the sidebar, organized by categories, order, nesting, and naming to provide an intuitive experience when learning and navigating.
The API Reference groups the HTTP methods for each URL. Within each page, there are inputs with types and examples that you can fill in to make a sample request. There are example response structures and values for each HTTP Response Code.
At the top of each page you'll find navigation tools labeled Search and Ask AI, which can locate resources from both the Guides and the API Reference.
- Clicking Search will show a standard filterable search modal, for you to browse through the relevant documentation pages.
- Clicking Ask AI will open a persistent chat session with Branch AI, which assembles a response for you using multiple sources within the documentation pages.
To use the documentation from your own AI assistant or code editor, connect it to the Branch MCP server.
Certify and Launch the Branch integration
Branch will supply test cases and your organization will provide recorded demos for each scenario. Branch will certify the integration in Sandbox before Production secret keys are provided. Align on key deployment dates with your Branch implementation consultant; Beta release is typically 2 to 3 weeks before general availability.
Updated 1 day ago
