Rate limiting
We have added rate limiting to our APIs (HTTP 429 Too Many Requests) to prevent fraudulent and
wrongful behavior, and to increase the stability and security of our APIs. The limits should
not affect normal behavior, but please contact us if you notice any unexpected behavior.
The Key column specifies what we consider to be the unique identifier, and
what we "use to count". The limits are of course not total limits.
The MSN is the unique identifier of the sales unit.
| API | Limit | Key | Explanation |
|---|---|---|---|
| Create | 5 per minute | reference + MSN | Five calls per minute for each unique reference |
| Capture | 5 per minute | reference + MSN | Five calls per minute for each unique reference |
| Cancel | 5 per minute | reference + MSN | Five calls per minute for each unique reference |
| Refund | 5 per minute | reference + MSN | Five calls per minute for each unique reference |
| Get a payment | 120 per minute | reference + subscription key | 120 calls per minute for each unique reference |
| Get payment event log | 120 per minute | reference + subscription key | 120 calls per minute for each unique reference |
Please note: The "Key" column is important. The above means that we allow 5
Create
calls per minute per unique reference for that MSN. This
is to prevent too many initiate calls for the same payment. The overall limit
for number of different payments is far higher than 5. The same goes for
Capture a payment:
You can make five capture calls per minute for
one unique reference, and the limit for capture calls for different reference values
is far higher.
You must send a reference property (with lower case) in your API request to avoid getting the HTTP 429 Too Many Requests warning.
If you don't provide it or if it's misspelled, then all your payment initiations will be considered as the same payment, and you'll meet the rate limitation.