When you send an HTTPS REST request to the Rapyd Payments platform, you must include specified header parameters, including a signature. These headers are required for both the production platform and the sandbox. The headers are not required in the response from your remote authorization server.

The signing process helps secure requests in the following ways:

Verifies that the requester is an authorized user. Protects data from tampering in transit. Rejects requests from unauthorized persons. When you send a request, you calculate the signature and insert the result into the signature header. When the platform receives the request, it performs the same signature calculation. If the resulting values do not match, the request is rejected.

• Make your first API Call with Rapyd Payments documentation: https://docs.rapyd.net/build-with-rapyd/docs/make-your-first-api-call
• Join the Rapyd Community: https://community.rapyd.net