Getting Started with DirecFunds

DirecFunds is a treasury management platform that gives title agencies and their banking partners a complete digital payment solution — covering incoming Good Funds and post-close disbursements using the supported commercial rails below. This guide walks you through everything you need to go from a new account to your first disbursement.

During registration, choose the products your company needs. DirecFunds enables each requested product after review. If your company uses only Due diligence payments, the buyer funds the property payment and you can complete setup without a company source bank account. Identity, billing, agreement, user, seller, and payment approval checks still apply. The bank-account and API disbursement steps below are for companies with Business disbursements enabled.
Due diligence workflow: An authorized brokerage agent completes DirecFunds' LexisNexis identity check once, then can start further transactions while that verification is current and their company access remains active. The agent can prepare a seller before a buyer or purchase contract exists. The seller completes identity and receiving-account verification through a private invitation. Once an executed contract exists, the agent records its reference and dates, attests to reviewing it, and adds the buyer and amount. Only then can the payment be submitted for independent approval. A buyer is not contacted at the seller-preparation stage.

Start an Experience API integration

  1. Confirm Business disbursement access. A company administrator creates the Test credentials in the Test portal under Manage → API Integration (see Enabling API Access).
  2. Obtain a token using https://direcfundstest2.b2clogin.com/direcfundstest2.onmicrosoft.com/B2C_1A_CLIENT_CREDENTIALS/oauth2/v2.0/token. See authentication and the separate Production endpoint.
  3. Read capabilities with your bearer token, then follow the first Test request using prepared fixtures.
  4. If features.webhooks is true in GET /Integration, configure and verify webhook delivery. Webhooks are enabled per integration and depend on the current integration configuration; the event feed is the authoritative record.
  5. Complete the onboarding and go-live readiness checks before Production use.

Platform payment rail support

These rails belong to the commercial payout platform. Account access, destination eligibility, payment windows, and funding readiness are checked separately.

Scroll the table to see environment availability.

Supported payout rails and managed company funding directions
RailRecipient payoutManaged company fundingEnvironment availability
ACHSupportedPayout onlyCheck authenticated capabilities
FedNow ServiceSupportedPayout onlyCheck authenticated capabilities
Real Time PaymentSupportedPayout onlyCheck authenticated capabilities
Same Day ACHSupportedSupportedCheck authenticated capabilities
Wire TransferSupportedSupportedCheck authenticated capabilities

Zelle disabled Zelle remains available on historical records and is excluded from new commercial payouts.

With your own bearer token, read GET /v1/PaymentRails for the environment rail contract and GET /v1/DisbursementRequests/Capabilities for bundled-request funding, payouts, and features. A missing or refused capability needs its actual reason checked; it does not automatically mean your account is disabled.

What You'll Need

Before you begin, make sure you have:

  • Access to the administrator email invitation so you can verify the address and create a password
  • Your company's source banking information if you will send Business disbursements
  • The names and emails of the staff who will be requesting and approving disbursements

Step 1 — Log In and Check Your Company

When your account is created during onboarding, a Company record is set up for you. This is the top-level object that holds your disbursement rules.

If your company registered through the portal, the registration confirmation means its information was received. The administrator must open the private, time-limited activation link sent by email and create a password before signing in. Check with DirecFunds support if the invitation does not arrive.

Log in to the DirecFunds portal and open Manage → Company to confirm your company name is correct. Review the approval strategy under Company → Approval preferences.

There are three approval strategies:

Strategy How it works
Single Party Approval An authorized user may request and approve within the company policy. Production fallback, limits and permissions can require a separate approver; read approvalRequirements.
Two Party Approval One user requests a disbursement; a second user must approve it before it is sent.
Single Party Approval with Limit A requester who also holds approve permission may approve their own disbursement below a set dollar amount. A disbursement at or above that limit, or one whose requester lacks approve permission, requires a separate approver. If no limit is configured, every disbursement requires a separate approver.

Company administrators can choose any of the three strategies unless DirecFunds has restricted the company's choices. Two Party Approval is always available. Contact DirecFunds support to change a restriction.

Step 2 — Set Up Your Address

Branch and bank-account setup collect their required address details.

Enter the address in the branch or bank-account setup form:

  • Street address (Address Line 1 is required; Lines 2–4 are optional)
  • City
  • State (two-letter code, e.g. OH, TX, FL)
  • Postal code (5-digit, or 5+4 format such as 45000-1234)

Step 3 — Confirm Your Branch

A default branch is automatically created when your company is onboarded, based on your company information. If your business operates out of a single location, this is all you need.

If you have multiple offices, you can add additional branches in the portal under Branches → Add Branch. Each branch requires an address and an optional phone number.

Step 4 — Add a Bank Account

Your bank account is the source of funds for disbursements. Go to Bank Accounts → Add Bank Account and provide:

  • Bank name
  • Beneficiary name (the name on file with the account)
  • Account number
  • Routing number
  • The address associated with the account
  • Which branches this account is available to

Bank setup checks the routing number with Bankers Almanac and fills the bank's directory details. Review any advisory shown. If the directory cannot validate the routing number, save is paused until the lookup succeeds or the number is corrected. Account ownership and ACH or wire capability are checked separately during verification.

Important: To fund live disbursements, your bank account needs either a reverse wire (drawdown) authorization on file with DirecFunds or verified Same Day ACH debit capability. You can add the bank account now; it becomes ready for funding once one of those is in place.
Billing: before anyone approves a disbursement, a company administrator must save a chargeable card or US bank account under Manage → Billing → Payment method. When billing payment-method enforcement is enabled, approval without one is refused with 422 BILLING_PAYMENT_METHOD_REQUIRED. Onboarding readiness does not check billing.

Step 5 — Add Your Users

Users are the employees who will create and approve disbursements. Go to Users → Add User and enter their name, email, and phone number, then assign their permissions. API-created users start active and non-administrator. API removal is a soft deactivation; the integration guide documents ETag-safe deactivation and reactivation.

Branch permissions control whether a user can request disbursements, approve them, or both — per branch.

Bank account permissions control which bank accounts a user can disburse from — per branch.

Example: Two Party Approval Setup

A common setup for title agencies using Two Party Approval:

  • Closing Agent (e.g. Bob) — assigned canRequest: true, canApprove: false on their branch. Can create disbursements but cannot approve or send them.
  • Escrow Manager (e.g. Alice) — assigned canRequest: false, canApprove: true across one or more branches. Can review and approve disbursements submitted by requesters.

This ensures no single person can both create and release a payment.

Step 6 — Create Your First Disbursement

Once your company, branch, bank account, and users are configured, you're ready to disburse. For a portal workflow, see the Disbursements Guide. For a server-to-server integration, begin with the Experience API Quickstart, which creates the funding and recipient-payment legs atomically through /DisbursementRequests. Partner implementations should use the partner onboarding guide to create and verify the trust account, assign it to a branch, configure payment authority, and wait for GET /Onboarding/Readiness before enabling that quickstart flow.

Enabling API Access

If your title software integration requires programmatic access to DirecFunds, API credentials can be generated directly in the portal. Use the Test portal for Test credentials and the Production portal for Production credentials:

  1. Log in as an administrative user
  2. Open Manage → API Integration in the left navigation
  3. Select Enable API integration

Your Client ID and Client Secret will be displayed. The secret is shown only once; store both in your secret manager. They are used to obtain OAuth 2.0 bearer tokens for all API calls. Rotate API credentials replaces the whole app registration: both the client ID and the secret change, and the old credentials stop working immediately, with no overlap window. Run the Experience API Quickstart first. Then use the API Integration Guide for the complete contract, operational guidance, and supported advanced granular workflow. Integration teams should also follow the partner onboarding guide for the exact ownership handoffs.

Getting Help

If you run into any issues during setup, email DirecFunds support at support@direcfunds.com or reach out to your onboarding representative.