> ## Documentation Index
> Fetch the complete documentation index at: https://developers.ingopayments.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Process — ACH

> Push a disbursement via Standard ACH, Same-Day ACH, or Real-Time rails.



## OpenAPI

````yaml specs/ingopay-process-ach.yaml POST /gateway/process--ach
openapi: 3.0.3
info:
  title: IngoPay API — Push Method ACH / Same-Day ACH / RTP
  description: >
    Submit a request to push funds to a customer's bank account via Standard
    ACH, Same-Day ACH, or Real-Time Payments (RTP).


    The partner and their customer should be committed to the payment prior to
    making this call. A successful response confirms the payment item has been
    accepted. **Once accepted, a payment cannot be reversed.**


    **`account_type` determines the rail:**

    - `AC` — Standard ACH

    - `SD` — Same-Day ACH

    - `RT` — Real-Time Payments (RTP)


    > **Assume Success:** Clients should assume success for any Process request
    where a response was not received from Ingo Payments, including assumption
    of normal settlement. Any consumer funds associated with the transaction
    should be accounted for aligning with normal successful transaction
    processing.


    > **Log Transaction ID:** Log the Ingo `transaction_id` and
    `participant_unique_id1` for every transaction — Ingo Payment Services will
    request these values for any support interactions.


    > **ACH character limits for `additional_detail`:** For ACH transactions,
    `source_name` and `descriptive_purpose` have a combined maximum of 21
    characters. The first 10 characters of `source_name` and the first 11
    characters of `descriptive_purpose` are always accepted — additional
    characters may be truncated depending on the length of the other field.
    `additional_detail` is not applicable for RTP (`RT`) transactions.
  version: '11'
  contact:
    name: Ingo Money Developer Support
    url: https://developers.ingomoney.com
servers:
  - url: https://payapi-sandbox.ingo.money
    description: Sandbox
  - url: https://payapi.ingo.money
    description: Production
security:
  - HmacAuth: []
paths:
  /gateway/process--ach:
    post:
      tags:
        - Push Payments
      summary: Push funds to a bank account via ACH, Same-Day ACH, or RTP
      description: >
        Initiates a push disbursement to a customer's bank account using a token
        from a prior Verify call. Set `account_type` to `AC` for Standard ACH,
        `SD` for Same-Day ACH, or `RT` for RTP.
      operationId: processACH
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ProcessACHRequest'
            example:
              participant_id: 12345
              account_type: AC
              amount: 1010.5
              customer_account_token: 89421718-a62e-4344-8a1d-4baf73fb11f1
              source_of_funds: 4
              recipient_phone: '1231231234'
              participant_unique_id1: 5bf1e2c3-2169-406f-bf1b-f7bc5c2303b3
              participant_unique_id2: 80525360-dae4-4d0f-9f5c-e09f3fdcf7c8
              additional_detail:
                source_name: CorpDisb
                descriptive_purpose: Reimbursement
              ledger:
                api_key: lk_live_abc123xyz
                user_id: usr_00456
                entity_type: program
                entity_id: ent_00789
              timestamp: 1576100703
              version: 11
      responses:
        '200':
          description: Payment accepted successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ProcessACHResponse'
              example:
                status: 100
                client_message: Success
                data:
                  estimated_posting_time: Payment will post 04/22/2026
                  estimated_posting_date: 04/22/2026
                  transaction_id: 2361537
                  request_timestamp: 1576100772
                  customer_account_token: 89421718-a62e-4344-8a1d-4baf73fb11f1
                  participant_unique_id1: 5bf1e2c3-2169-406f-bf1b-f7bc5c2303b3
                  participant_unique_id2: 80525360-dae4-4d0f-9f5c-e09f3fdcf7c8
                time: '1.3092'
        '400':
          description: Validation error — check request body
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              example:
                status: 604
                client_message: Insufficient funds
                data:
                  request_timestamp: 1576100772
components:
  schemas:
    ProcessACHRequest:
      type: object
      required:
        - participant_id
        - timestamp
        - version
        - amount
        - participant_unique_id1
        - account_type
        - source_of_funds
        - customer_account_token
      properties:
        participant_id:
          type: integer
          description: Unique participant identifier assigned by Ingo.
          example: 12345
        timestamp:
          type: integer
          format: int64
          description: Unix timestamp of the request.
          example: 1576100703
        version:
          type: integer
          description: API version of the request. Current version is 11.
          example: 11
        amount:
          type: number
          format: float
          minimum: 0.01
          description: Amount of the transaction.
          example: 1010.5
        participant_unique_id1:
          type: string
          minLength: 1
          maxLength: 255
          description: >
            Participant assigned transaction ID for the process request. Value
            must be unique and may not contain NPI data. Used for idempotency —
            a duplicate value returns an idempotent response without initiating
            a new push request. Appears on daily reconciliation reports.
          example: 5bf1e2c3-2169-406f-bf1b-f7bc5c2303b3
        account_type:
          type: string
          enum:
            - AC
            - SD
            - RT
          minLength: 1
          description: >
            Determines the payment rail. `AC` = Standard ACH, `SD` = Same-Day
            ACH, `RT` = Real-Time Payments (RTP).
          example: AC
        source_of_funds:
          type: integer
          enum:
            - 1
            - 2
            - 3
            - 4
          description: >
            Funding source indicator: 1 = Cash, 2 = Check, 3 = Combo of Cash &
            Check, 4 = Corp Disbursement.
          example: 4
        customer_account_token:
          type: string
          minLength: 1
          maxLength: 255
          description: >
            Token representing the account number and customer data as provided
            in the response from a previous Verify API call.
          example: 89421718-a62e-4344-8a1d-4baf73fb11f1
        recipient_phone:
          type: string
          maxLength: 10
          nullable: true
          description: 10-digit recipient phone number.
          example: '1231231234'
        participant_unique_id2:
          type: string
          maxLength: 255
          nullable: true
          description: >
            Optional second participant assigned transaction ID. Does not appear
            on daily reconciliation reports.
          example: 80525360-dae4-4d0f-9f5c-e09f3fdcf7c8
        additional_detail:
          type: object
          nullable: true
          description: >
            Additional transaction details specific to the account type.
            Applicable for `AC` and `SD` only — exclude for `RT` (RTP)
            transactions. For ACH, `source_name` and `descriptive_purpose` have
            a combined maximum of 21 characters.
          properties:
            source_name:
              type: string
              maxLength: 50
              nullable: true
              description: >
                Name of the transaction source as easily recognizable to the
                receiver. For ACH, the first 10 characters are always accepted —
                additional characters may be truncated depending on the length
                of `descriptive_purpose`.
              example: CorpDisb
            descriptive_purpose:
              type: string
              maxLength: 50
              nullable: true
              description: >
                Description of the purpose of the transaction. For ACH, the
                first 11 characters are always accepted — additional characters
                may be truncated depending on the length of `source_name`.
              example: Reimbursement
        store_id:
          type: string
          maxLength: 255
          nullable: true
          description: |
            Client assigned store ID. Required for Retail client participants.
          example: STORE-001
        clerk_id:
          type: string
          maxLength: 255
          nullable: true
          description: |
            Client assigned clerk ID. Required for Retail client participants.
          example: CLK-007
        terminal_id:
          type: string
          maxLength: 255
          nullable: true
          description: >
            Client assigned terminal ID. Required for Retail client
            participants.
          example: TERM-042
        ledger:
          $ref: '#/components/schemas/Ledger'
    ProcessACHResponse:
      type: object
      properties:
        status:
          type: integer
          description: >
            Numeric code describing the status of the API request. 100 =
            Success.
          example: 100
        client_message:
          type: string
          description: Text description associated with the status code.
          example: Success
        data:
          type: object
          properties:
            estimated_posting_time:
              type: string
              description: Provided on success. Estimated posting time narrative.
              example: Payment will post 04/22/2026
            estimated_posting_date:
              type: string
              description: Provided on success. Estimated posting date.
              example: 04/22/2026
            transaction_id:
              type: integer
              description: >
                Always provided on success and in certain failure conditions.
                Unique transaction identifier. Log this value — Ingo Payment
                Services will request it for support interactions.
              example: 2361537
            request_timestamp:
              type: integer
              format: int64
              description: Unix timestamp of the request.
              example: 1576100772
            customer_account_token:
              type: string
              description: Echo of value from request. Provided on success.
              example: 89421718-a62e-4344-8a1d-4baf73fb11f1
            participant_unique_id1:
              type: string
              description: >
                Always provided on success and in certain failure conditions.
                Echo of value provided on request.
              example: 5bf1e2c3-2169-406f-bf1b-f7bc5c2303b3
            participant_unique_id2:
              type: string
              nullable: true
              description: >
                Provided on success and in certain failure conditions if sent on
                original request. Echo of value provided on request.
              example: 80525360-dae4-4d0f-9f5c-e09f3fdcf7c8
        time:
          type: string
          description: Time in seconds to complete the request.
          example: '1.3092'
    ErrorResponse:
      type: object
      properties:
        status:
          type: integer
          example: 604
        client_message:
          type: string
          example: Insufficient funds
        data:
          type: object
          properties:
            request_timestamp:
              type: integer
              format: int64
              example: 1576100772
    Ledger:
      type: object
      description: >
        Required for clients configured for ledger service. Exclude entirely if
        not applicable to your integration.
      required:
        - api_key
        - user_id
        - entity_type
        - entity_id
      properties:
        api_key:
          type: string
          minLength: 1
          maxLength: 100
          description: API key associated with the ledger program.
          example: lk_live_abc123xyz
        user_id:
          type: string
          minLength: 1
          maxLength: 100
          description: User ID associated with the ledger program.
          example: usr_00456
        entity_type:
          type: string
          minLength: 1
          maxLength: 50
          enum:
            - program
            - business
            - user
          description: >
            Entity type for the ledger. Accepted values: `program`, `business`,
            `user`.
          example: program
        entity_id:
          type: string
          maxLength: 100
          nullable: true
          description: Entity ID associated with the ledger.
          example: ent_00789
  securitySchemes:
    HmacAuth:
      type: http
      scheme: hmac-sha512
      description: >-
        HMAC-SHA512 signed Authorization header. See the Authentication page for
        the complete signing guide.

````