A. Get started

We use UTC

As previously mentioned, each Api request must be authenticated prior to be processed. Therefore, client-side applications will need to sign each request with a specific authorization header. When working on the authentication mechanism, the development team took as a...

A number of Customate's entities - including Profile, Payee, Funding source, Schedule and Payment - have a metadata field. Clients can use this field for storing additional, structured information on an object. As an example, corresponding unique identifiers from...

Customate Api follows common HTTP principles and will respond with appropriate status codes with each request. In general: codes in the 2xx range indicate successful operation. Codes in the 4xx range indicate an error that typically relates to the incoming request...

Customate applies rate limits on the Api calls a client’s integration can make within a given time period. If this limit is exceeded the request will be throttled and marked as failed. By default, clients' applications are able to make up to 600 GET requests per...

The authorization functionality serves to track incoming calls for each Api key and enforce the selected terms of service. In application architecture terms, the authorization module is located in the front-end of the application and it is called immediately after the...

Just like any payment service, Customate focuses on the security of our customers and their data. Development team constantly works to ensure the safety of information regardless of any possible failures in application. There are several points worth mentioning: All...

Background This knowledge base contains general information about the Customate Api. Customate offers virtual bank accounts in multiple currencies, supports bank transfers in and out, open banking in, digital direct debits, real-time customer onboarding, provides...