Skip to main content
POST
Process an eCheck sale

Authorizations

Authorization
string
header
required

Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.

Body

application/json

API support various types of use. Required fields are defined by the most basic call. For other uses be sure to send the required information defined in the schema and examples.

subMerchantId
string
required

Unique identifier of the submerchant.

amount
number
required

The amount to debit.

paymentToken
object
required

The payment credential to charge: a one-time token from the web component or a stored Jupico token.

description
string

Free-text description.

customerId
string

Unique identifier of the customer.

checkNumber
string

Check number to record with this debit.

checkType
string

Type of check used for the debit.

taxAmount
number

Sales tax portion of the amount.

referenceId
string

Your own reference for this transaction. Returned in responses and query results for reconciliation.

dynamicFee
object

Fee added to the transaction at processing time and itemized separately.

billing
object

Billing contact and address details for the payer.

shipping
object

Shipping contact and address details for the order.

metadata
object

metadata is an object that can host as much as 50 key-value pairs, where the keys can be at most 40 char length and can’t include the characters “[“ or “]”, and the values must be strings and cannot exceed 500 chars Learn more about metadata

Response

200 - application/json

Successful eCheck operation

data
object

The response payload.

success
boolean

Whether the request was processed successfully. Declines return HTTP 200 with success: false.

message
string

Human-readable result message.

code
string

Machine-readable result code. See the Error Codes reference.

Last modified on July 14, 2026