Skip to main content
Hurdlr’s impending Quarterly Tax Payments API allows you to provide your clients with seamlessly integrated 1040-ES payments to the IRS for federal estimates. This high value functionality can be provided to your users on its own. However, as you continue down your roadmap, you will find that using this functionality in conjunction with other features in the Hurdlr ecosystem result in a powerful solution that connects all the dots.

​
1. Creating a user

Once you have registered a user, you can easily set your user up to send out 1040-ES estimated payments to the IRS.
📘 Future use cases By registering a user in the Hurdlr API, you also gain access to the rest of the Hurdlr API’s products. As you build out your roadmap, you can gradually start utilizing additional Hurdlr functionality with little-to-no overhead. For example, payments made via the Quarterly Tax Payments API are automatically tracked in the Accounting system, which enables many future use cases.

​
2. Track your user’s finances (optional)

In addition to allowing you to simply make quarterly estimated payments to the IRS, the Hurdlr API enables the more complex task of tracking all your user’s finances. After connecting your data sources, all transactions are then run through Hurdlr’s proprietary algorithms, which leverage the user’s business type, accountant best practices, and the behavior of similar users within the Hurdlr app’s 700k+ users. That data can then be instantly leveraged throughout Hurdlr’s APIs, which include expense categorization, tax categorization, financial reporting, tax estimates, tax reporting, tax filing, and many other features.
📘 No front-end development You can also quickly and easily embed Hurdlr’s white-labelled UI into your product, removing the need for front-end development.
If your data sources are connected to the Hurdlr API, you can easily/instantly get accurate tax estimates, to allow your user to make a more informed estimated payment.

​
3. Add tax filer info

You should update the following fields on your user’s tax payment profile, all of which are required in order to submit payments to the IRS:
FieldDescriptionFromat
address1First line of your user’s home addressAny string
address2Second line of your user’s home addressAny string
cityCity of your user’s home addressAny string
stateState of your user’s home addressTwo-character string
zipZip code of your user’s home addressAny string
phonePersonalYour user’s personal phone numberString containing numbers only
dateOfBirthYour user’s date of birth”YYYY-MM-DD”, e.g. “1985-12-15”
ssnYour user’s social security numberString containing numbers only
👍 Personally Identifiable Information All of the above fields are considered Personally Identifiable Information (PII), and are therefore stored in a separate database, not accessible via the internet, encrypted at the individual field level. For more information on our privacy/security measures, vetted by major U.S. banks, don’t hesitate to email us at api@tight.com.
To update the user’s tax payment profile, simply POST the completed JSON object to the /userTaxPaymentSetup endpoint: 
curl \
  --request POST \
  --url https://sandbox.hurdlr.com/rest/v5/taxes/userTaxPaymentSetup \
  --header 'Authorization: Bearer ${access_token}' \
  --header 'Content-Type: application/json' \
  --data '{
    "userTaxPaymentSetup": {
      "address1": "1815 Adams Mills Rd NW",
      "address2": "#3",
      "city": "Washington",
      "state": "DC",
      "zip": "20009",
      "phonePersonal": "2025555555",
      "dateOfBirth": "1985-12-15",
      "ssn": "555555555"
    }
  }'

​
4. Add payment info

Payments to the IRS can be made using ACH, which requires capturing the bank account number (accountNo) and routing number (routingNo). Once you’ve captured that info from your user, you can simply POST the completed JSON object to the /paymentInfo endpoint: 
curl \
  --request POST \
  --url https://sandbox.hurdlr.com/rest/v5/taxes/paymentInfo \
  --header 'Authorization: Bearer ${access_token}' \
  --header 'Content-Type: application/json' \
  --data '{
    "paymentInfo": {
      "method": "ACH",
      "accountNo": "1234567890123",
      "routingNo": "123456789"
    }
  }'
Note: Payment info is treated as PII and therefore handled with the utmost security. For more information on our privacy/security measures, please email us at api@tight.com.

​
5. Submit quarterly tax payment to the IRS

To submit a quarterly estimated payment to the IRS, you will need to assemble the following fields into a JSON object:
FieldDescriptionFormat
periodPeriod of the estimated paymentMust be one of the following: “Q1”, “Q2”, “Q3”, “Q4”
yearYear for which the estimated payment will be madeNumeric, with 4 digits (e.g. 2021)
amountTotal value of the paymentNumeric, with 2 decimal places
paymentInfoIdOptional; Id of the paymentInfo to make the payment from. Defaults to most recently added paymentInfo.Numeric
Simply POST the completed JSON object to the /estimatedPayment endpoint: 
curl \
  --request POST \
  --url https://sandbox.hurdlr.com/rest/v5/taxes/estimatedPayment \
  --header 'Authorization: Bearer ${access_token}' \
  --header 'Content-Type: application/json' \
  --data '{
    "estimatedPayment": {
      "period": "Q2",
      "year": 2021,
      "amount": 1022.28
    }
  }'

​
6. Next steps

Whether you are building your own UX from scratch or have some existing functionality that you are looking to enhance, the Hurdlr API team is here to help optimize your tax payment experience. Don’t hesitate to email us at api@tight.com, and we would be glad to help you create and complete the best next steps for your product and vision. To learn more about how to manage tax payments after they’ve been submitted, please take a look at our “Managing Tax Payments” documentation.