Overview

    sequenceDiagram

    participant M as Merchant/LMS
    participant A as Auth
    participant F as Flex API / CORE
    participant O as Flex OPS Team
    participant B as Bank
    
    critical Verification
        M->>A: 1. Request Token
        A->>M: 2. Token Verified + Sent Back
    end


    M->>F: 3. Send Transaction(s) to Flex
    Note over F: Queued
    F->>M: 4. Transaction confirmation sent back

    
    F->>O: 5. Send Payment Info
    Note over O: Verification
    O-->>M: 6. ItemStatus updates to "S" when item is ready to be sent to Bank
    O->>O: 7. Built Files
    O->>B: 8. Send payment files

ACH Transaction Example

Automated Clearing House (ACH) is a common and cost-effective method to move payments between U.S. bank accounts. It’s ideal for payroll, vendor payments, and recurring billing.

While slower than real-time methods, ACH is reliable and suited for high-volume transfers.

1. Create an ACH Transaction

Creating an ACH Transaction begins with submitting a payment using the single or bulk instructions. At this stage, you’ll provide details such as:

• Originating and receiving account
• Amount
• SEC code
• Optional metadata or reference IDs

Once submitted, the transaction enters a pending state as it is queued for batching and settlement.

Cutoff Time

ACH cutoff times vary by provider. Check with provider for specific times.

2. Retrieve an ACH Transaction

There are many ways to view the status of a transaction and parameters, so please check our page for getting transactions and use the desired endpoint.

Possible statuses include:

• pending: Awaiting processing within ACH cut-off window
• submitted: Sent to the ACH Network
• settled: Funds have cleared and posted
• returned: The transaction failed

If the transaction is returned, you’ll receive a return code and a timestamp indicating when the return was processed.

Return Codes

You can view the full API documentation in our Swagger Collection. This collection provides detailed information about all available endpoints, including request and response schemas, parameters, and examples.

3. Void an ACH Transaction

Voiding an ACH transaction is only possible before it is batched or submitted to the network. Once submitted, the transaction is out of our hands and must follow the return process.

View our page for voiding transactions and use the desired endpoint.

If a transaction successfully voids, the status will be updated to voided.