ACH tokens are used to replace actual bank and account details sent for processing a transaction. For example, you can store an ACH token with a customer and/or a subscription contract in your application and use the token to process a payment when required.

Parameters

The following fields are available to create an ACH token.

parameter	description	required
profile_id	Merchant supplied customer id	No
cnickname	a nickname that the cardholder would like to save	No
acccount_type	the type of account: `1 = personal checking` `2 = personal savings` `3 = corporate checking` `4 = corporate savings`	Yes
name_on_acccount	the account holders full name	Yes
account_number	the bank account number	Yes
routing_number	the bank routing number (RTN)	Yes
baddress	the account street address	No
bcity	the account city name	No
bstate	the account state code	No
bzip	the account zip code	No
cphone	the account holders phone number (mobile)	No
cemail	the account holders email address	No
store	set this to `0` to create a temporary token (much like a payment intent) if not present default = `1`	No

Example

The following JSON example provides test values to create an ACH token. You can copy and replace these values in the transaction_data object in the Try it Out feature

{
  "transaction_data": {
  	"acccount_type": "1",
  	"name_on_acccount": "Jerry Smith",
  	"account_number": "5544044490909090",
  	"routing_number": "5544044490909090",
  	"baddress": "26776 Chesterton Drive",
  	"bcity": "Indianapolis",
  	"bstate": "IN",
  	"bzip": "46280"
  }
}

References

Link to details on related response codes.
Payment Response Codes