Bank Account Verification — Proposed Guide

Planned API — Reference Only

Bank Account Verification: Verification could establish whether a repayment instrument meets a provider requirement. It does not by itself prove that an…

Overview

Verification could establish whether a repayment instrument meets a provider requirement. It does not by itself prove that an expense is authorized or that a payment may proceed.

Key concepts

Model pending, verified and failed outcomes with a verification reference. Decide who may view the supporting evidence.

Implementation considerations

No microdeposits or verification calls are performed. Provider requirements and permissible verification methods remain future design inputs.

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": "Bank Account Verification",
  "verification_id": "verification_example_123",
  "payment_method_id": "payment_method_example_123",
  "verification_status": "verification status example",
  "occurred_at": "2026-01-15T12:00:00Z"
}

Design review checklist

Document which organization owns the bank account verification representation and which actor may view or change it.
Test the boundaries of verification id, payment method id, verification status, occurred at 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
verification_id	string	Stable fictional verification 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.
verification_status	string	Illustrative verification status value; interpret it only within the proposed topic-specific model described above.
occurred_at	string (date-time)	Synthetic UTC timestamp. Business occurrence time may differ from delivery or processing time.

Bank Accounts

Reimbursements & Payments

Payment Initiation