Acquiring Status Codes

HTTP

Error Handling

A 400 Series Error is usually something that you can fix by changing something in your request.
A 500 Series Error is usually something that you need to contact us ([email protected]) to look at.
1. If we determine that a 500 Series Error can be fixed by you, we will try to change this error situation to a 400 Series Error in a future code release.
If you receive a 207 while using any resource, please contact [email protected] for assistance.

Production HTTP Status Code 400

If you are getting a HTTP Status Code of 400 on the Production Environment, that usually means you are not handling these errors correctly on your end. We strongly recommend completing the Production Certification Test in its entirety, specifically the portion where we recommend integrating your application with our API calls.

HTTP Status Code 207

You might get HTTP Status Code 207, when there is an error while processing your transaction due to some Upstream Process.
Everything on our end processed successfully:

Your request passed all our checks
Configuration is available to process your request
A record is created for your request (Transaction)

Volume Spikes

If not inform of unexpected Volume Spikes, our systems may detect the activity as abnormal and may block all IP Addresses causing the unexpected volume of requests. Volume Spikes that are all (or mostly) Errors, like:

SC=404 coming from Retrieve Transactions
SC=409 coming from Create Accounts or Create Transactions

will expedite this block of IP Addresses.