An authentication mechanism where the client must provide a token (JWT) in the HTTP Authorization header to authenticate requests. More information here
A URL where the payment gateway sends updates about the transaction status after processing. The merchant must set this URL to receive notifications about payment results.
A testing environment that mimics the live production environment but does not execute real transactions. It allows developers to simulate transaction scenarios without financial impact.
A request made by the client to add funds to a user's account through various payment methods (e.g., card payments). This involves transferring funds from the client’s account into the merchant’s system.
A request made by the client to remove funds from their account, typically involving transferring money from the merchant’s system to the client’s external account (bank or other financial institution).
An API call to retrieve the current status of a transaction or order. Merchants use this to verify if a payment has been completed, failed, or is pending.
A service that processes payment information between the merchant and financial institutions. It handles transaction authorization, routing, and settlement of funds.
The business or entity using the PayStar system to accept payments from customers. Merchants configure their API settings and handle transactions for their products or services.
The Card Verification Value, a 3- or 4-digit code, typically found on the back of the card. It is used as a security measure to verify that the card is in the possession of the cardholder.
This defines the size of the challenge window used in 3D Secure authentication, with codes like 01, 02, 03, etc., corresponding to specific window sizes.
