Skip to content

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.

License

Notifications You must be signed in to change notification settings

Rapyd-Samples/rapyd-request-signatures

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Rapyd Request Signatures Code Sample

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.

Demo Video (YouTube)

thumbnail of video link for youtube video showing rapyd request signatures video

Resources

About

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.

Topics

Resources

License

Security policy

Stars

Watchers

Forks

Languages

  • JavaScript 100.0%