Bring Your Own Ledger (BYOL) with EDAS
Overview
The Bring Your Own Ledger (BYOL) model allows clients to maintain their own internal system of record while leveraging EDAS for compliant, bank-backed deposit account infrastructure. This model is ideal for platforms that want full control over their accounting logic, user experience, and financial workflows—while still benefiting from the regulatory and operational support of a scaled banking partner. In BYOL, clients can match actual funds held in the custodial account to the balances reflected in the client’s system.
This page provides a consolidated view of the payment capabilities supported by EDAS, including ACH, Wire, Real-Time Payments (RTP), and Book Transfers. It outlines how these payment types interact with two key account identification methods—Virtual Reference Numbers (VRNs) and Client-Provided Account Numbers—and whether each scenario supports API-based integration.
Virtual Reference Numbers (VRNs)
VRNs are virtual identifiers that act as aliases to end-users within the Newline platform. They are used to receive payments (such as ACH or wire transfers) but do not represent real bank accounts, hold balances, or initiate outbound payments.
- Used for: Receiving payments only
- Not used for: Sending payments, holding balances
- Common use case: Using VRNs to tag incoming payments and associate them with the correct end user’s synthetic account for ledger updates and reconciliation.
The payment capabilities matrix indicates “Yes” where a payment type and direction are supported using VRNs or client-provided account numbers, as outlined in the corresponding tables.
Payment Product Capabilities Matrix
Use this matrix to determine which payment types and directions are supported for your integration, based on whether you're using VRNs or client-provided account numbers. For implementation details, refer to the corresponding API documentation.
Payment Type | Direction | VRNs | API Support | Notes |
---|---|---|---|---|
ACH | Send | Yes | Yes | Standard and Same-Day supported SEC Codes Supported CCD, PPD, WEB, TEL, and CIE. |
ACH | Receive | No | Yes | NACHA files accepted, Domestic only |
Wire | Send | No | Yes | Domestic only |
Wire | Receive | Yes | Yes | Domestic only |
RTP | Send | No | Yes | Real-time push payments |
RTP | Receive | No | No | Availability may vary by bank |
Book Transfers | Internal | – | Yes | Between internal accounts only |
Payment Type Overviews
EDAS supports multiple payment rails to accommodate a range of business needs, from low-cost batch transfers to real-time disbursements. Below is an overview of the supported payment types, including key characteristics and processing details.
ACH (Automated Clearing House)
ACH transfers enable low-cost movement of funds between U.S. bank accounts. EDAS supports both credit and debit ACH transactions, including Standard and Same-Day processing. Transfers are not instant and typically settle in 1–2 business days. Newline handles NACHA formatting, submission, and status tracking. International ACH transactions are currently unsupported. Support may be introduced in a future release.
Wire Transfers
Wire transfers support secure, high-priority USD payments via the Federal Reserve or CHIPS networks. EDAS currently supports domestic wires only. Transfers are final and processed individually throughout the business day. International Wire transactions are currently unsupported. Support may be introduced in a future release.
Real-Time Payments (RTP)
RTP enables near-instantaneous fund transfers, 24/7/365. EDAS supports RTP for use in cases like payroll or instant disbursements. RTP is push-only and does not currently support VRNs or client-provided account numbers.
Book Transfers
Book transfers are internal movements of funds between accounts within the same institution. These are supported via API and do not involve external payment networks.
Updated about 6 hours ago