Checks

Parameters

This page provides details about the required and optional parameters for checks fraud protection. To ensure a successful request, you must include all the required fields. The optional fields offer additional functionality but are not necessary for initiating a successful request.

Fetch check exceptions

Use these query parameters to retrieve check exceptions.

Fetch check exceptions
Field	Description	Minimum	Maximum	Notes
`exceptionType`	Exception type for which to fetch exceptions.			Enum: POSITIVE_PAY, REVERSE_POSITIVE_PAY.
`status`	Filter exceptions by status.			Enum: PENDING_DECISION, DECISIONED.
`limit`	The maximum number of results to return. This parameter is used for pagination and limits the number of exceptions returned in the response.	1	100
`offset`	This is the page number used for pagination. It is a 0-based value. For an initial search, use 0. To retrieve the next page, increment by 1.	0	999

Submit decision for a check exception

Use these parameters to submit a decision for a specific check exception.

Required fields

Required
Field	Description	Minimum	Maximum	Notes
`id`	Unique identifier assigned by JPM for Positive Pay exception.	1	99	Type: string (ExceptionId). Example: n8a40v3r-3769-4o79-9z0l-ale1edc90389.
`decision`	Decision submitted for a check exception.			Object (ExceptionDecision).
`decision.type`	Decision type.			Enum: PAY, RETURN.
`revision.checkAmount.amount`	A string representation of a (potentially) decimal positive number.	1	11	Required. Type: string (Decimal). Pattern: ^\d+(\.\d+)?$.
`revision.checkAmount.currency`	ISO 4217 Alpha-3 currency code.	3	3	Required. Type: string (IsoCurrencyCode). Pattern: ^[A-Z]{3}$.

Optional fields

Optional fields
Field	Description	Minimum	Maximum	Notes
`Idempotency-Key` (header)	Client-generated unique idempotency key that enables safe retries.	1	255
`revision`	Revised check details (if applicable).			.
`revision.checkNumber`	Check number as assigned by the agent.	1	10	.
`revision.checkAmount`	Check amount.			.

Conditional fields

Conditional fields
Field	Description	Minimum	Maximum	Notes
`decision.returnReason`	Decision reason.			Required when `decision.type` is RETURN. Not required when `decision.type` is PAY. Select one enum value from the Positive Pay reason table.

Positive Pay reason table

Positive Pay reason table
Value	Description
`RTN_REFER_TO_MAKER`	A return reason indicating the bank is directing the payee to contact the issuer (the "maker") for resolution. When no specific reason is chosen, systems may default to Refer to Maker J.P.
`RTN_ALTERED_AMOUNT`	The dollar amount on the check does not matching issued details.
`RTN_ALTERED_PAYEE`	The payee name does not match the original issued details.
`RTN_CHECK_STOPPED`	The issuer placed a stop-payment order.
`RTN_DUPLICATE_ITEM`	The same check has been presented more than once (duplicate paid record) within the same recon period.
`RTN_IMP_ENDORSEMENT`	The endorsement does not meet client standards.
`RTN_INVALID_SIGNATURE`	The signature appears not genuine or not authorized for the account.
`RTN_LOST_STOLEN`	The check was reported lost or stolen. Payment is declined to prevent unauthorized use.
`RTN_NO_ENDORSEMENT`	No endorsement is present where one is required to negotiate the check.
`RTN_NO_SIGNATURE`	The issuer's signature is absent.
`RTN_POST_DATE`	The check is dated in the future and was presented before the effective issue date.
`RTN_SEE_CHECK`	RTN-See Check.
`RTN_SIGNATURE`	A general signature irregularity (for example, differs from specimen or requires verification).
`RTN_STALE_DATE`	The check is presented after the client's defined stale-date period.
`RTN_STOP_PAY`	The issuer placed a stop-payment order.
`RTN_SUSPECT_ITEM`	The check is flagged for potential fraud.

Next steps

Review available resources for check fraud protection.