Process an eCheck sale
Initiates a direct debit (ACH) from the customer’s bank account. If the debit request is accepted, the transaction proceeds to settlement; otherwise the response includes the failure reason. Note that ACH returns can occur days after acceptance.
Authorizations
Basic authentication header of the form Basic <encoded-value>, where <encoded-value> is the base64-encoded string username:password.
Body
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.
Unique identifier of the submerchant.
The amount to debit.
The payment credential to charge: a one-time token from the web component or a stored Jupico token.
Free-text description.
Unique identifier of the customer.
Check number to record with this debit.
Type of check used for the debit.
Sales tax portion of the amount.
Your own reference for this transaction. Returned in responses and query results for reconciliation.
Fee added to the transaction at processing time and itemized separately.
Billing contact and address details for the payer.
Shipping contact and address details for the order.
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
Successful eCheck operation

