Authentication Methods
In online and mobile payments, security is a number one concern. Authentication and verification of the identity of the cardholder is important for preventing fraudulent transactions and refunds.
Each request to Judopay’s Transaction API requires authentication.
Depending on how you integrate with Judopay, the following methods are recommended to authenticate requests:
- /paymentsession
- /paymentsession, or
- TokenSecretAuth
- The token and secret pair
It is recommended to use /paymentsession to authenticate your requests, as this flow supports the full payment flow handling Customer Initiated Transactions for alternative payment methods and 3D Secure transactions.
This method of authentication ensures that any intermediate steps are handled automatically by Judopay.
We also recommend using paymentSession when authorising /payments or /preauths for 3D Secure 2 transactions for the same reason.
Store the reference returned in the response in your backend server. Then Invoke a /payments or /preauths transaction using the paymentSession reference.
Make a HTTP POST Request: /paymentsession
Your backend server should store the paymentSession response reference returned by Judopay's API.
Use this reference from the response to populate paymentSession when calling /payments and /preAuths from your front-end client.
The following parameters need to remain consistent between the /paymentsession requests and the /payments and /preauths requests, otherwise the transaction will fail:
- YourPaymentReference
- YourConsumerReference
- JudoID
- Currency
- Amount This is used to cross reference the validity of the transaction.
When authorising /payments or /preauths you can call directly to the API using:
- /paymentsession
- TokenSecretAuth
- The token and secret pair
- Specify your token in Username and secret in Password
For more information on creating a /paymentsession, see Transaction API /paymentSession.
For more information on headers to authenticate a transaction using TokenSecretAuth, see Authenticating using TokenSecretAuth.
Prerequisites
- You are using Judopay's API version 6.0.0.0 or higher.
- You have the /paymentsession response reference.
The paymentSession will expire in 30 minutes, unless an ExpiryDate is set in the /paymentsession request body.
Request Message Structure:
Request Message Structure: