Automated Bank Pull Funding Launched

Everflow Pay has introduced an in-app bank pull (automatic debit) funding method. This release eliminates the manual effort and errors associated with traditional ACH and wire transfers, allowing clients to fund their accounts directly within the platform.

Introduction

Historically, Everflow Pay clients (payers) had to manually push funds via ACH or wire to their Funding Wallet. This manual process relied on users correctly entering a specific Reference ID in the transfer's memo field. If omitted or entered incorrectly, funds would fail to route, leading to missing funds disputes, operational overhead, and delayed partner payouts.

To resolve this friction, Everflow Pay has integrated direct bank pull capabilities. US-incorporated clients using US or Canada bank accounts can now securely connect a bank account, manage their funding source, and initiate precise pull requests directly within the Everflow Pay interface. This structural shift automates the transfer initiation and eliminates the risk of misrouted funds.

Key Capabilities

• Direct Bank Account Connection: Clients can securely input their banking details within the Everflow Pay interface to add and manage a single, tokenized funding source.
• In-App Pull Requests: Users can initiate exact funding requests directly from the UI, with a minimum request limit of $10 enforced.
• Contextual Guidance: The funding interface displays the total amount of unpaid invoices to guide users in determining their pull request amount.
• Status and Deposit Tracking: An enhanced Deposits section displays historical and active funding requests, distinguishing between pull and push funds, with statuses mapped from the system (such as Sent, InProgress, and Complete).
• Strict Impersonation Audit Trails: To support troubleshooting, Customer Success agents can impersonate clients to manage funding, with the system enforcing a strict audit log capturing the Base User, Impersonator ID, IP Address, Date/Time, Transaction Amount, and Transaction ID.
• System Safeguards: The integration includes backend safeguards to prevent duplicate transactions, alongside velocity checks to flag anomalies and limit liability.

Under the Hood

• Transition to Pull-Based Flows: Expanded the system integration to handle transactions under an automated, tokenized pull model that resolves in up to 5 working days.