Create a payment

post

https://test-api.payology.io/api/v1/payment

Create an X9 check payment. This edition focuses payment examples and schema on X9; the proxy also has ACH/CC selectors outside this payment scope. Replace both TIFF markers before sending. 201 is creation, not settlement. 202 and the image-related 422 responses can also contain a newly created payment_token; reconcile it before resubmitting.

Result codes in the response examples

HTTP status and result code are operation-specific. Field-validation messages can include the affected field name.

HTTP	Code	Result	Meaning
201	R0000	Ok	The request was processed successfully
202	R0115	Ok	Surpassed allowed limit
202	R0116	Error	The payment is duplicated
400	R0001	Error	field is required
400	R0002	Error	Field is not properly formatted
400	R0101	Error	Organization Bank Account token is inactive
400	R0102	Error	Organization Bank Account token is invalid
400	R0118	Error	Reference_id already exists
400	R0202	Error	Organization is inactive
401	R0003	Error	Authentication token is invalid
403	R0003	Error	Access not allowed
422	R0451	Error	Front image non-conforming
422	R0452	Error	Rear image non-conforming
500	R0999	Error	Something went wrong

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Responses

default

Other infrastructure or forwarded downstream response. HTTP status and body must be preserved; do not assume every error has a Payology R-code. No fixed payload is guaranteed.

Language

Credentials

Header

URL

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

201Check created. It may be pending processing or MICR review.

202Record created with an exceptional business outcome. Do not interpret 202 as approval.

400Invalid fields, selector, or business rule. Consult the individual example code.

401Authentication failed. Some services also use 401 for organization access denial. Gateway bodies can differ.

403Permission or organization access denied; the gateway can reject the request before it reaches the service.

413Proxy JSON body exceeds the configured 1 MiB limit; base64 images count toward that limit.

422A payment record was created with a non-conforming TIFF image. Malformed base64 can instead fail initial validation with 400.

429Gateway throttling or quota. Exact quota, retry headers and deployed body were not verified. This is a platform possibility, not an observed Payology response.

500Unhandled service failure. Gateway configuration/authorizer failures can also return 500.

502Proxy could not obtain an HTTP response from the selected payment service.

504Gateway integration timeout or failure. The service may still have committed a create request. This is a platform possibility, not an observed Payology response.