Follow the steps below to create a domestic payment consent. The same steps with minor changes can be followed for other types of payment consents.
First, in the collections, under Payments, open the Get Access Token request and click Send.
If your environment was set up properly, there is no need to change any parameter.
The request returns a JSON containing an access_token, which is automatically saved to the access_token environment variable.
There's no need to copy the value; it will automatically be used in the following requests.


ConsentId value. This value is automatically saved to the environment variable consentId.
code parameter from this URL. You will need it in the next step.When creating the consent, our custom pre-request script automatically calculates the JWS signature of the request body using your private
key and saves it into the jws_signature environment variable, which is then used in the x-jws-signature header of the request.
code parameter which was retrieved from the previous redirect URI and click Send.

In the response, you see a JSON with an access_token parameter.
This has automatically been saved to the payments_access_token environment variable for later use.

Data.ConsentId key-value pair required in this request. Use the consent ID you received when creating the consent.You can use {{consentId}} as in the default request body to use the consentId environment variable which was automatically saved previously.
See the screenshot above.
jws_signature environment variable.In the response, you get the result of the payment.