Check Payments

Check payments are often confused with ACH payments. Although they both utilize the customers' bank account to make a payment, check transactions are a more manual process. Check transactions refer to a customer handing the merchant a physical check. That check must be taken by the Merchant to the bank in order for the funds to be processed and deposited into their account. Whereas, ACH transactions require less management from the merchant as they simply enter the banking information through a virtual terminal and the rest is done for them, no more trips to the bank for deposits.

Use Cases

  • Merchants who want to offer additional payment methods to their customers.

Things to Keep in Mind

Please note, check transactions are simply for reporting purposes only, this means the merchant is still required to manually deposit the checks in order for the funds to be deposited into their account. Although checks and ACH differ when it comes to how the bank information is obtained and deposited they share the same shortcomings. Several days may pass before you're alerted that a check was fraudulent or rejected due to insufficient funds. Customers have the power to issue a “stop payment” on any check they write. These are important to keep in mind for Merchants performing services or goods, as customers can essentially write you a check, take your services or product, and then take their money back.

Step 1

  • Set HTTP request method to POST and use /payment route

Step 2

  • Supply the request with your username and password. Make sure it's in base-64 encryption in the Authorization header field.
  • Set Content-Type to Application/JSON

Step 3

  • In the bankAccount object, the required fields may vary based on your merchant fraud settings. The name field is always required, but phone and checkNumber are optional.
         "name":"John Doe",