Our API generates a signed request header using the webhook URL, POST, key, secret and the webhook data: http_method = "POST" headers = generate_signed_request_headers(url, http_method, credential.key, credential.secret, data) generate_signed_request_headers()...
Background The tables below describe the timings and the different transaction statuses for the most common type of scenarios. Money into a wallet Scenario Timings to credit the Customate wallet Possible different statuses Open banking transfer to Wallet The...
Here is how it works on an example of a “Webhook creation” call:
Webhook events will be sent to a specified URL, not at the time the event was created, but with a certain frequency (several seconds). In this case, several events may accumulate for the profile during this waiting time. All of them will be divided into batches of 10...
HMAC token Each webhook POST request is signed with an HMAC token, that was generated with the same secret that Customate has provided to the client and webhook event id as a key. It is required that the client validates this token before starting event processing....
Processing webhook events may be crucial for the clients' business logic, so the Customate team wants to make sure that our clients will receive webhook events from Customate, even in case of temporary issues on their side. To increase the chance of this, Customate...
Endpoints Related endpoints reference. How we use webhooks Working with various types of payments involves the appearance of asynchronous events, whether it is a change in funding source status or the execution of a scheduled payment. Customate uses webhooks to notify...