ACH Reimbursements — Proposed Guide

Planned API — Reference Only

ACH Reimbursements: An ACH proposal would require an approved payment provider, eligible account references and a defined funding process. ACH batch…

Overview

An ACH proposal would require an approved payment provider, eligible account references and a defined funding process. ACH batch acceptance differs from settlement and can be followed by a return.

Key concepts

Track submission, provider acknowledgment and later settlement or return as distinct facts. Record a provider reference without exposing account numbers.

Implementation considerations

No ACH connection or transfer is available. Timing, return windows, eligibility and regional availability must be verified with an approved provider.

Illustrative data model

This local fixture shows a possible representation for the concepts above. It is not an endpoint response, production configuration or a claim that the described capability is implemented.

JSON fixture

Fictional concept fixture

{
  "reference_only": true,
  "topic": "ACH Reimbursements",
  "reimbursement_id": "reimb_example_123",
  "payment_method_id": "payment_method_example_123",
  "provider_reference": "provider_example_123",
  "status": "draft"
}

Design review checklist

Document which organization owns the ach reimbursements representation and which actor may view or change it.
Test the boundaries of reimbursement id, payment method id, provider reference, status using synthetic values, including missing or inconsistent references.
Before future implementation, obtain an approved contract and review failure behavior. This documentation does not authorize production activation.

Proposed data types

Illustrative field dictionary
Name	Type	Description
reimbursement_id	string	Stable fictional reimbursement reference; not a secret and not evidence that a resource exists.
payment_method_id	string	Stable fictional payment method reference; not a secret and not evidence that a resource exists.
provider_reference	string	Fictional provider correlation reference, not settlement evidence.
status	string	Proposed lifecycle value. Its meaning depends on the resource and must not be inferred from HTTP success.

Reimbursement Status

Reimbursements & Payments

Payment Methods