ACH Limits Overview
Sila's authorization framework evaluates interactions between end users and its API service. In all cases where Limits are applied, a request is both authenticated and authorized. As part of the process of authorization, Sila's API identifies requests that exceed the threshold set by a service quota. Limits cause requests to fail when a service quota has been exceeded.
INTRODUCTION TO END USER ACH LIMITS ON SILA’S PLATFORM
Sila utilizes ACH limits per end-user account to its platform. ACH limits are a standard across our industry. They represent healthy boundaries to ensure the health and well-being of the Sila platform and all businesses that transact on it, including end-users.
API Limits
- /transfer and /redeem transactions do not have limits
- These limits impact the end user
- Some API endpoints have limits
- Sila returns an error when a request exceeds a limit
- Limits may cap the end users ability to transact by looking at their transaction history, gathering data about their current balances or evaluating the total requests you make to our API’s protected endpoints
What are the end-user limits that are being imposed?
As a reminder, listed below are the standard ACH limits per end-user. If every end-user stays within these limits, there is no impact on your business or your application. Limits are calculated per user, for a given KYC Level, and on a rolling 24-hour, 7-day, and 30-day period. Furthermore, end users cannot transact beyond the applicable dollar amount for the duration of the rolling window.
- KYC Debit Limits
Maximum Rolling 24-hour limit: $10,000
Maximum Rolling 30-day limit: $30,000 - KYB Debit Limits
Maximum Rolling 24-hour limit for KYB: $50,000
Maximum Rolling 30-day limit for KYB: $150,000
What will the end-user see if they reach their limit?
Clicking on the link will show examples of limits related response headers .
- As a developer, you will want to catch limit related messaging and build an appropriate end user interface that will be displayed in lieu of the error message.
Example
A KYC user with no previous transaction requests in 24 hours:
| Action: | Consequence: |
|---|---|
| 9 am (day 1): The user requests a $9,000 debit | For the next 24 hours the user can request up to $1,000 worth of ACH debits |
| 3pm (day 1): The user requests a $1,000 debit | For the next 18 hours, they cannot conduct any further ACH debits because they have reached their 24-hour limit |
| 9:01 am (next day): It is 24 hours after the initial request, the user can now request up to $9,000 again but does nothing | |
| 3:01 pm (next day): The user’s rolling 24-hour limit has reset back to $10,000 |
How can you better understand the limits and help your end-users?
Please see the Limits - Technical Details for more detailed information about the limits and how they are triggered within the API.
Updated about 1 year ago
The following are supporting documentation for ACH Limits