Verify

Authorizations

Authorization

string

header

required

All requests must be authenticated using an HMAC-signed Authorization header. Ingo Money requires HMAC-SHA512 for all new integrations. SHA-512 provides a significantly larger internal state and output length than SHA-256, making it substantially more resistant to length-extension attacks and brute-force preimage attempts — properties that matter for financial API traffic where each request authorizes a real money movement.

Legacy integrations using HMAC-SHA256 remain supported but are encouraged to upgrade. SHA-256 continues to meet the current minimum security bar; however, upgrading to SHA-512 eliminates an entire class of potential vulnerabilities before they become exploitable, and aligns with NIST guidance recommending SHA-2 family algorithms with 256-bit security strength or greater for long-term use. Contact your Ingo integration manager to coordinate an algorithm upgrade.

MD5 and SHA-1 are not accepted under any circumstances. Requests signed with either algorithm will be rejected.

Authorization header format:

Authorization: hmac username="YOUR_HMAC_USERNAME", algorithm="hmac-sha512", headers="request-line x-date content-type content-length content-sha512", signature="BASE64_SIGNATURE"

Credentials provisioned by your Ingo integration manager:

HMAC username — identifies your integration in the Authorization header username field. Distinct from your participant identifier.
HMAC secret — provisioned by your Ingo integration manager. The private key used to compute the signature. Never transmit this value — store it in a secrets manager or environment variable, never in source code.
Participant identifier — a separate value used to identify your account within the API request payload. The name and placement differs by product family. Both the HMAC username and participant identifier are provisioned at onboarding — do not substitute one for the other.
API key — required for select product families as an additional per-request credential. See product-specific documentation for applicability.

See the Ingo API Authentication Guide for the complete string-to-sign construction, body hashing requirements, and timestamp validation rules.

Body

application/json

Provide either customer_account_token or the raw account fields (account, recipient_first_name, recipient_last_name, recipient_address1, recipient_city, recipient_state, recipient_zip) — never both.

participant_id

integer

required

Unique participant identifier assigned by Ingo.

Example:

12345

payee_id

string

required

Ingo assigned payee ID for the selected biller. Obtain from the Biller Payments Search API prior to calling Verify.

Maximum string length: 40

Example:

"123457"

timestamp

integer<int64>

required

Unix timestamp of the request.

Example:

1587052132

version

integer

required

API version of the request. Current version is 11.

Example:

11

participant_unique_id1

string

required

Participant assigned ID to be associated with customer_account_token creation. Should correlate to participant assigned values affiliated with future process requests for tracking purposes (e.g. CustomerID or AccountID). Must not contain NPI data.

Required string length: 1 - 255

Example:

"f8f68709-8e5d-4c19-8ca0-2eaffef4ec57"

account_type

enum<string>

required

Always BP for bill payment transactions.

Available options:

BP

Minimum string length: 1

Example:

"BP"

customer_account_token

string | null

Alternative to raw account data when the account was previously tokenized. If provided, the following fields are not required and should be omitted: account, recipient_first_name, recipient_last_name, recipient_address1, recipient_city, recipient_state, recipient_zip.

Required string length: 1 - 255

Example:

"a74eacf4-32e8-4081-b69c-565a89dd6cf1"

account

string

Customer bill payment account number. Required unless a valid customer_account_token is provided.

Required string length: 1 - 255

Example:

"12345678"

recipient_first_name

string

Customer first name. Required unless a valid customer_account_token is provided.

Required string length: 1 - 255

Example:

"Johnny"

recipient_last_name

string

Customer last name. Required unless a valid customer_account_token is provided.

Required string length: 1 - 255

Example:

"Rockets"

recipient_business_name

string | null

Optional recipient business name.

Maximum string length: 150

Example:

"Rockets LLC"

recipient_address1

string

Customer billing address line 1. Required unless a valid customer_account_token is provided.

Required string length: 1 - 255

Example:

"123 Main St"

recipient_city

string

Customer billing city. Required unless a valid customer_account_token is provided.

Required string length: 1 - 255

Example:

"Atlanta"

recipient_state

string

Customer billing state (standard US postal abbreviation). Required unless a valid customer_account_token is provided.

Required string length: 2

Pattern:

^(?:A[LKSZRAEP]|C[AOT]|D[EC]|F[LM]|G[AU]|HI|I[ADLN]|K[SY]|LA|M[ADEHINOPST]|N[CDEHJMVY]|O[HKR]|P[ARW]|RI|S[CD]|T[NX]|UT|V[AIT]|W[AIVY])$

Example:

"GA"

recipient_zip

string

Customer billing zip code. 5-digit zip or zip+4 in xxxxx-xxxx format. Required unless a valid customer_account_token is provided.

Maximum string length: 10

Pattern: ^[0-9]{5}(?:-[0-9]{4})?$

Example:

"30313"

recipient_address2

string | null

Customer billing address line 2.

Maximum string length: 255

Example:

"Apt 2"

recipient_email

string | null

Optional recipient email address.

Maximum string length: 255

Example:

"johnny.rockets@example.com"

recipient_phone

string | null

10-digit recipient phone number.

Maximum string length: 10

Example:

"1231231234"

participant_unique_id2

string | null

Optional second participant assigned ID to be associated with customer_account_token creation. Should be carried forward to future process requests for tracking purposes. Must not contain NPI data.

Maximum string length: 255

Example:

"257b5bae-d52f-42e2-8f2c-0700d8d7a7a5"

amount

number<float> | null

Dollar amount of disbursement. Max value determined by participant velocity limits.

Required range: x >= 0.01

Example:

1010.5

Response

Verification successful — token returned

status

integer

Numeric code describing the status of the API request. 100 = Success.

Example:

100

client_message

string

Text description associated with the status code.

Example:

"Success"

data

object

Hide child attributes

data.customer_account_token

string

GUID — unique value generated based upon account and recipient data. Use this token in all subsequent Process requests for this account.

Example:

"a74eacf4-32e8-4081-b69c-565a89dd6cf1"

data.last_4

string

The last 4 digits of the account number.

Example:

"5678"

data.request_timestamp

integer<int64>

Unix timestamp of the request.

Example:

1587052142

data.issuers

object[]

Information about the issuer (biller).

Hide child attributes

data.issuers.payee_id

string

The Ingo assigned ID for the payee.

Example:

"123457"

data.issuers.payee_name

string

Name of the payee (biller).

Example:

"First Service Middle Jersey"

data.issuers.payee_address

string | null

Payee address.

Example:

"PO Box 5555"

data.issuers.payee_city

string | null

Payee city.

Example:

"Secaucus"

data.issuers.payee_state

string | null

Payee state.

Example:

"NJ"

data.issuers.payee_zip

string | null

Payee zip code.

Example:

"07032-0310"

data.issuers.credit_info

object

Information regarding limits for push (credit) transactions. Returned if participant is enabled for push processing.

Hide child attributes

data.issuers.credit_info.min

string

Minimum amount accepted for a push transaction.

Example:

"5.00"

data.issuers.credit_info.max

string

Maximum amount accepted for a push transaction.

Example:

"2000.00"

data.issuers.credit_info.card_type

string

Account type identifier.

Example:

"NA"

data.issuers.credit_info.estimated_posting_time

string

Estimated posting time narrative.

Example:

"Payment will post 04/17/2026"

data.issuers.credit_info.estimated_posting_date

string

Estimated posting date.

Example:

"04/17/2026"

data.issuers.issuing_network

string

Issuing network identifier.

Example:

"NA"

data.issuers.credit_enabled

enum<integer>

Whether the account is enabled for push (credit) transactions. 1 = Enabled, 0 = Not enabled.

Available options:

0,

1

Example:

1

data.issuers.debit_enabled

enum<integer>

Whether the account is enabled for pull (debit) transactions. 1 = Enabled, 0 = Not enabled.

Available options:

0,

1

Example:

0

data.participant_unique_id1

string

Echo of participant assigned ID for the verify request.

Example:

"f8f68709-8e5d-4c19-8ca0-2eaffef4ec57"

data.participant_unique_id2

string | null

Echo of optional second participant assigned ID for the verify request.

Example:

"257b5bae-d52f-42e2-8f2c-0700d8d7a7a5"

data.count

integer

Number of issuers returned.

Example:

1

time

string

Time in seconds to complete the request.

Example:

"1.6832"

Overview

Process

Debit

Risk

Ancillary

Webhooks

Verify — BillPay

Authorizations

Body

Response

Overview

Verify

Process

Debit

Risk

Ancillary

Webhooks

Documentation Index

Authorizations

Body

Response