Skip to main content

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.

APILimitKeyExplanation
Create5 per minutereference + MSNFive calls per minute for each unique reference
Capture5 per minutereference + MSNFive calls per minute for each unique reference
Cancel5 per minutereference + MSNFive calls per minute for each unique reference
Refund5 per minutereference + MSNFive calls per minute for each unique reference
Get a payment120 per minutereference + subscription key120 calls per minute for each unique reference
Get payment event log120 per minutereference + subscription key120 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.

Help us improve our documentation

Did you find what you were looking for?