Accept simple and secure payments in your app or website with Judopay’s SDKs. Quickly capture your customer’s card details for immediate payments or save them securely for future payments.

Then, you will receive access to your Judopay dashboard and the sandbox environment.

To follow the steps to quickly integrate and produce a test card payment using Judopay’s Web SDK, see Start Integrating with Judopay.

You can have:

A judoId can be allocated for a route or location basis. Multiple judoIds can also be created to take into account a more granular set of transaction reporting, for example to separate online transactions, the location where transactions took place, or the most used payment method.

All judoId's can have different configurations enabled.

You will receive your API credentials when setting up your account with Judopay. These credentials control the permissions enabled on your sandbox and live token and secret pair(s).

Each Token and Secret pair will have specific permissions configured.

The following illustration provides a helpful overview on the permissions that need to be set up, in order for each step in the payment flow to be able to take place:

Depending on the payment methods, currencies and card schemes you want to accept, you can configure these specifically, (for example Visa, Mastercard, Apple Pay, Card, PayPal), or set to accept All.

Check your judoIds and tokens are configured and enabled as appropriate.

Interact with our Transaction API Reference in the following ways:

For more information, see How to use our Transaction API Reference Documentation.

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:

For more information, see Authentication Methods.

Prior to Testing - Prerequisites

Make sure you have the following set up prior to testing:

You need your sandbox account so you can process test transactions while developing your app.

The purpose of the sandbox environment is to allow you to test and replicate various use cases, payment flows and scenarios that your app should support.

Use the Test Cards and data to test your integration is working correctly. This will give you confidence that all is working as expected when your integration goes live.

For more information see, Testing your Direct (API) Integration.

For more information see, Testing Web Payments - Card Payments.

For more information see, Testing your Mobile SDK Integration.

For more information see, Testing Web SDK - Card Payments.

For more information see, Testing Digital Wallet Payments - via API.

For more information see, Testing Digital Wallet Payments - via Web SDK.

For more information see, Testing your Wallet Payment Integration.

Familiarise yourself with the key terms we use, to help you with your integration:

The judoId is a unique ID supplied by Judopay, which you add to the request body of each transaction request.

You will receive your API credentials when setting up your account with Judopay. These credentials control the permissions enabled on your sandbox and live token and secret pair(s).

Each Token and Secret pair will have specific permissions configured. For more information, see Token and Secret App Permissions.

3D Secure 2.0 aims to improve the security and consumer experience, including helping merchants achieve Strong Customer Authentication (SCA) compliance under PSD2.

The Payment Services Directive (PSD2), has introduced a new regulatory requirement: Strong Customer Authentication (SCA). The aim of the SCA is to add an increased layer of security for card not present transactions, when making mobile and online payments.

In the 3D Secure 2 payment flow, the Issuer will make a decision on whether they have enough authentication data to proceed with the transaction, or if they require the cardholder to further authenticate the transaction with additional Strong Customer Authentication (SCA) checks. For more information, see Improving Authentication in your Payment Flow.

To authenticate the transaction, merchants can verify the consumer's identity with the Issuer. To be compliant with SCA, 3D Secure 2 transactions have additional authentication and transaction information within the payment flow. For more information on 3D Secure 2, see What is 3D Secure?

Merchant-Initiated-Transactions (MIT)s, for example:

For more information, see Merchant Initiated Transactions.

Use the card token in the request body, instead of the card number. The card token is a randomly generated string linked to a card saved securely within the Judopay Card Vault.

You will not take on additional PCI scope, as the card token does not have any sensitive card information, so it can be stored in your database.

Alternative Payment Methods refers to a range of payment methods beyond the traditional ways of paying with cards and cash.

Currently Judopay accepts the following alternative payment methods:

Integrate Apple Pay™ and Google Pay™ via Web and Mobile.

For more information, see Wallet Payments.

A minimal integration is all that is required to enable you to take a payment.

Generate hosted payment page links using Judopay’s Transaction API and redirect the consumer back to your own website, using configured redirect URLs.

This helps minimise your PCI scope by providing consumers with a secure way to pay online via their browser, optimised for any device.

For more information, see Web Payments.

Judopay’s SDKs enables merchants to easily integrate and customise a seamless consumer checkout experience, for Mobile, Web and Server integrations.

All of our SDKs come built-in with the following features:

If you prefer to use your own UI for the consumer’s checkout journey, you can still easily integrate with Judopay using only a few lines of code to begin accepting payments.

For more information, see: