In App Bank Pulls for EF Pay

Everflow has introduced an in-app bank pull (automatic debit) funding method for EF Pay, eliminating the need for manual, error-prone push transfers. This release allows platform operators to securely connect a bank account and initiate precise funding requests directly within the EF Pay interface. By automating the deposit workflow, this update streamlines account funding and prevents payment delays caused by missing or incorrect reference details.

Introduction

Previously, EF Pay clients had to manually push funds via ACH or Wire to their Funding Wallet. This process heavily relied on the user entering a specific Reference ID in the transfer's memo field. If this ID was omitted or typed incorrectly, funds would fail to route to the client's account, resulting in missing funds disputes, manual tracking overhead, and delayed partner payouts.

To resolve this friction, Everflow has integrated direct bank pull capabilities. US-incorporated clients can now securely connect a US or Canadian bank account directly within the EF Pay Wallet to initiate direct debits. This shift to an in-app pull model automates the transaction flow, drastically reducing deposit errors and administrative support times.

Key Capabilities

• Direct Bank Account Connection: Connect and manage a single US or Canadian bank account securely within the EF Pay interface using a custom banking details form.
• In-App Pull Requests: Initiate precise funding requests directly from the UI, with contextual guidance displaying the total amount of unpaid invoices to help determine the deposit size.
• Enhanced Deposit Tracking: View a detailed history of funding requests, including clear indicators for push versus pull funds, request dates, and real-time transaction statuses.
• Pending Deposits State: Track uncleared transactions via a dedicated "Pending Deposits" status, preventing users from attempting to spend funds before they have fully cleared.
• Automated Alerts and Notifications: Receive in-app status updates and automated email notifications when a funding request is in progress, succeeded, or failed.
• Secure Impersonation and Audit Logs: Enable Customer Success agents to manage funding on behalf of clients with strict audit logging that captures the impersonator ID, IP address, timestamp, and transaction details.

Safeguards

• Tokenized Security: Utilizes tokenized bank information, ensuring sensitive routing and account numbers remain fully encrypted and hidden from platform users.
• Idempotency Safeguards: Enforces backend checks to block duplicate requests and prevent accidental double-billing.