Testing Web SDK - Card Payments

Testing Web SDK - Card Payments
With Judopay’s Web SDK solution, a minimal integration is all that is required to enable you to:
Take a card payment
Take a card preAuth
Take a card token payment
Take a card token preAuth
Check the validity of a card, using checkCard
﻿
Prerequisites
Before attempting Web SDK test transactions, ensure the following steps have been implemented:
﻿Step One: Create a paymentSession﻿﻿
﻿Step Two: Add the Payment Form to your Website﻿﻿
Defined the payment configuration, token configuration and check card configuration objects as required.
﻿
Card Payment Scenarios (Positive Flow)
Important to Consider
yourPaymentReference is your unique reference for each transaction.
Ensure you generate a unique yourPaymentReference and unique paymentSession for each transaction.
This will avoid duplicate transactions.
When making token payments, yourConsumerReference must match the original reference when the token was initially created.
Ensure the following information in your configuration object(s) matches the information in the paymentSession:
judoId
currency
amount
yourConsumerReference
yourPaymentReference
If this does not match, you will receive an error.
Suggested Test Scenario
Expected Outcome
Tip
Process a successful Web SDK card checkCard request.
This will check the card is valid.
200
Successful
Ensure you have defined the check card configuration object.
The checkCard response provides the:
cardToken
yourConsumerReference
Ensure you use the correct cardToken and yourConsumerReference to make future token payments, otherwise they will fail.
Process a successful Web SDK card payment / preAuth request.
 
200
Successful
Ensure you have defined the payment configuration object.
The payment /preAuth response provides the:
cardToken
yourConsumerReference
Process a Web SDK card token payment / preAuth with the CV2 / CVV security code included in the request.
This will check the CV2 / CVV and card token are valid and match the stored card details.
200
Successful
The consumer will not be prompted to enter the security code.
Ensure you have defined the token configuration object. where securityCode is set and shouldVerifySecurityCode=false
When making token payments or preAuths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
Process a Web SDK card token payment prompting the consumer to enter just their cardholder name.
﻿
Set:
shouldVerifyCardholderName: true
shouldVerifySecurityCode: false
If cardHolderName is provided in the configuration object, it will be overwritten with the value entered here.
When making token payments or preAuths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
Process a Web SDK card token payment prompting the consumer to enter just their card security code.
﻿
Set:
shouldVerifySecurityCode: true
shouldVerifyCardholderName: false
If securityCode is provided in the configuration object, it will be overwritten with the value entered here.
When making token payments or preauths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
Process a Web SDK card token payment prompting the consumer to enter both their cardholder name and security code.
﻿
Set:
shouldVerifyCardholderName: true
shouldVerifySecurityCode: true
When making token payments or preauths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
3D Secure 2 Flows
For each 3D Secure 2 scenario, different calls are made from the front end to the back end. 
It is advised to be aware of the different results from each flow and how your app will handle these.
﻿
﻿
Process a Web SDK card payment prompting the frictionless flow.
﻿Testing 3D Secure 2 Flows (Frictionless Flow)﻿﻿
﻿
Ensure Judopay has enabled 3D Secure 2 on your sandbox tokens.
If 3D Secure 2 is not enabled on your tokens, the test transaction will be successful, however it will not have followed the 3D Secure 2 verification process.
Process a Web SDK card payment prompting the non-frictionless flows.
﻿Testing 3D Secure 2 Flows (Non-Frictionless Flow)﻿﻿
﻿
Ensure Judopay has enabled 3D Secure 2 on your sandbox tokens.
If 3D Secure 2 is not enabled on your tokens, the test transaction will be successful, however it will not have followed the 3D Secure 2 verification process.
For more information on API credentials and permissions, see Permissions﻿.
﻿
Test Data
To simulate a successful web payments request, use the Test Cards﻿.
﻿
﻿
Request Parameters
Taking a card payment or preAuth:
Define the configuration object for the payment or preAuth.
Add the .invokePayment call to invoke a payment using the paymentSession and configuration object.
Add the .invokePreauthcall to invoke a preAuth using the paymentSession and configuration object.
Making a check card request:
Define the configuration object for the checkCard.
Add the .invokeCheckCard call to make a Check Card request using the paymentSession and configuration object.
Taking a card token payment or token preAuth:
Define the configuration object for the token payment or token preAuth.
Add the .invokeTokenPayment call to invoke a payment using the paymentSession and configuration object.
Add the .invokeTokenPreauth call to invoke a preAuth using the paymentSession and configuration object.
Header Parameters:
These header parameters are to be used when creating the paymentSession - (Prerequisite)﻿ request to our Transaction API. 
For more information, see Authentication Methods﻿.
﻿
﻿
Body Parameters:
Web SDK Payment / preAuth / CheckCard / Token Payment Configuration Parameter Descriptions:
﻿
Request Example
Response Example
const paymentConfiguration = {
    judoId: "yourJudoId",
    amount: 1.01,
    currency: "GBP",
    phoneCountryCode: "44",
    challengeRequestIndicator: "challengeAsMandate",
    initialRecurringPayment: false,
    yourConsumerReference: "yourConsumerReference",
    yourPaymentReference: "yourPaymentReference",
    billingAddress: {
        address1: "My house",
        address2: "My street",
        town: "My town",
        postCode: "TR14 8PA",
        country: "826"
    },
    mobileNumber: "07999999999",
    emailAddress: "[email protected]",
    primaryAccountDetails: {
        name: "Doe",
        accountNumber: "9999999",
        dateOfBirth: "1989-09-19",
        postCode: "AB1 2CD"
    }
}
const paymentConfiguration = {
    judoId: "yourJudoId",
    amount: 1.01,
    currency: "GBP",
    phoneCountryCode: "44",
    challengeRequestIndicator: "challengeAsMandate",
    initialRecurringPayment: false,
    yourConsumerReference: "yourConsumerReference",
    yourPaymentReference: "yourPaymentReference",
    billingAddress: {
        address1: "My house",
        address2: "My street",
        town: "My town",
        postCode: "TR14 8PA",
        country: "826"
    },
    mobileNumber: "07999999999",
    emailAddress: "contact@judopay.com",
    primaryAccountDetails: {
        name: "Doe",
        accountNumber: "9999999",
        dateOfBirth: "1989-09-19",
        postCode: "AB1 2CD"
    }
}
﻿
﻿
Card Payment Scenarios (Negative Flow)
Declines can occur for various reasons, it can be impossible to simulate all the negative flows in a sandbox environment.
Important to Consider
How your app handles negative flows
Your customer's experience should a negative flow occur:
Logic to communicate error messages
Customise how your app responds
How to maintain application consistency
Follow our suggested guidelines to simulate negative scenarios, to test your app’s error handling:
Suggested Negative Test Scenario
Expected Error Code
Error Description
Attempt to perform a Web SDK card payment / preAuth / checkCard request decline using the following:
cardNumber: 4221690000004963
cv2: 452
expiryDate: 12/24
Declined
 
Card declined.
Attempt to perform a Web SDK card payment / preAuth / checkCard request gateway error
using the following:
cardNumber: 4976350000006891
cv2: 341
expiryDate: 12/25
The transaction request has passed all Judopay's validation checks.
The next step in the payment flow is for the gateway to perform their checks.
A gateway error occurs when for example, the gateway verifies the request details with the issuing bank, who declines the request as there are not enough funds in the account.
This response contains the receiptId.
Declined
 
Card declined.
Attempt a Web SDK card payment / preAuth with the Incorrect currency entered for the specified transaction.
Default currency = GBP
72
Sorry, we're currently unable to route this transaction. Please check your account details and try again.
If this issue persists, please contact customer services.
This is a processing error﻿.
Attempt to perform a Web SDK card payment 3D Secure 2 challenge flow, where the user taps the cancel button on the challenge screen.
Ensure you have set the correct flags to control the 3D Secure 2 challenge scenarios.
165
Unable to process transaction. Card authentication failed with 3DS Server.

Attempt to perform a Web SDK card payment / preAuth / checkCard request with the incorrect environment (live or sandbox) for your API Token and API Secret and configuration.
7
Sorry, we were unable to authorize this request. Please check your details and permissions before trying again.
Attempt to perform a duplicate transaction, re-using a yourPaymentReference that has already been used in a previous transaction.
86
Sorry, this payment has been stopped as it is a duplicate transaction.
Attempt to perform a Web SDK card payment / preAuth / checkCard request where the amount set in the configuration object is different to the amount set in the paymentSession.
12
Sorry, we were unable to process your payment. Please check your details and try again.
Attempt to perform a Web SDK card payment / preAuth / checkCard request where the card type used, is not supported on your Judopay account.
For example, if AMEX is not enabled on your account, use card type = AMEX.
73
Sorry, but this card type is not currently supported on this account.
Attempt to perform a Web SDK card payment / preAuth / checkCard request where the card scheme used, is not defined in the iFrame configuration object.
For example, if AMEX is not defined, use card scheme = AMEX.
//An array of card schemes that are accepted by the merchant.
//If this field is set, an error will appear if an unsupported card scheme is entered.
allowedCardSchemes: ['visa','mastercard'],
﻿
For the purpose of this exercise the class is named judopay-errors, and sets a style to be red. You can add any custom style you wish in your .CSS file.
<div class="judopay-errors" style="color:red">Error Location</div>
For more information, see Step Two: Add the Payment Form to your Website.﻿﻿
﻿
For a list of possible error codes, types and descriptions, see  Error Codes and Descriptions﻿.

Suggested Test Scenario	Expected Outcome	Tip
Process a successful Web SDK card checkCard request. This will check the card is valid.	200 Successful	Ensure you have defined the check card configuration object. The checkCard response provides the: cardToken yourConsumerReference Ensure you use the correct cardToken and yourConsumerReference to make future token payments, otherwise they will fail.
Process a successful Web SDK card payment / preAuth request.	200 Successful	Ensure you have defined the payment configuration object. The payment /preAuth response provides the: cardToken yourConsumerReference
Process a Web SDK card token payment / preAuth with the CV2 / CVV security code included in the request. This will check the CV2 / CVV and card token are valid and match the stored card details.	200 Successful	The consumer will not be prompted to enter the security code. Ensure you have defined the token configuration object. where securityCode is set and shouldVerifySecurityCode=false When making token payments or preAuths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
Process a Web SDK card token payment prompting the consumer to enter just their cardholder name.		Set: shouldVerifyCardholderName: true shouldVerifySecurityCode: false If cardHolderName is provided in the configuration object, it will be overwritten with the value entered here. When making token payments or preAuths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
Process a Web SDK card token payment prompting the consumer to enter just their card security code.		Set: shouldVerifySecurityCode: true shouldVerifyCardholderName: false If securityCode is provided in the configuration object, it will be overwritten with the value entered here. When making token payments or preauths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
Process a Web SDK card token payment prompting the consumer to enter both their cardholder name and security code.		Set: shouldVerifyCardholderName: true shouldVerifySecurityCode: true When making token payments or preauths, the cardToken and yourConsumerReference must match the original reference when the token was initially created.
3D Secure 2 Flows For each 3D Secure 2 scenario, different calls are made from the front end to the back end. It is advised to be aware of the different results from each flow and how your app will handle these.
Process a Web SDK card payment prompting the frictionless flow. Testing 3D Secure 2 Flows (Frictionless Flow)		Ensure Judopay has enabled 3D Secure 2 on your sandbox tokens. If 3D Secure 2 is not enabled on your tokens, the test transaction will be successful, however it will not have followed the 3D Secure 2 verification process.
Process a Web SDK card payment prompting the non-frictionless flows. Testing 3D Secure 2 Flows (Non-Frictionless Flow)		Ensure Judopay has enabled 3D Secure 2 on your sandbox tokens. If 3D Secure 2 is not enabled on your tokens, the test transaction will be successful, however it will not have followed the 3D Secure 2 verification process.

Suggested Negative Test Scenario	Expected Error Code	Error Description
Attempt to perform a Web SDK card payment / preAuth / checkCard request decline using the following: cardNumber: 4221690000004963 cv2: 452 expiryDate: 12/24	Declined	Card declined.
Attempt to perform a Web SDK card payment / preAuth / checkCard request gateway error using the following: cardNumber: 4976350000006891 cv2: 341 expiryDate: 12/25 The transaction request has passed all Judopay's validation checks. The next step in the payment flow is for the gateway to perform their checks. A gateway error occurs when for example, the gateway verifies the request details with the issuing bank, who declines the request as there are not enough funds in the account. This response contains the receiptId.	Declined	Card declined.
Attempt a Web SDK card payment / preAuth with the Incorrect currency entered for the specified transaction. Default currency = GBP	72	Sorry, we're currently unable to route this transaction. Please check your account details and try again. If this issue persists, please contact customer services. This is a processing error.
Attempt to perform a Web SDK card payment 3D Secure 2 challenge flow, where the user taps the cancel button on the challenge screen. Ensure you have set the correct flags to control the 3D Secure 2 challenge scenarios.	165	Unable to process transaction. Card authentication failed with 3DS Server.
Attempt to perform a Web SDK card payment / preAuth / checkCard request with the incorrect environment (live or sandbox) for your API Token and API Secret and configuration.	7	Sorry, we were unable to authorize this request. Please check your details and permissions before trying again.
Attempt to perform a duplicate transaction, re-using a yourPaymentReference that has already been used in a previous transaction.	86	Sorry, this payment has been stopped as it is a duplicate transaction.
Attempt to perform a Web SDK card payment / preAuth / checkCard request where the amount set in the configuration object is different to the amount set in the paymentSession.	12	Sorry, we were unable to process your payment. Please check your details and try again.
Attempt to perform a Web SDK card payment / preAuth / checkCard request where the card type used, is not supported on your Judopay account. For example, if AMEX is not enabled on your account, use card type = AMEX.	73	Sorry, but this card type is not currently supported on this account.
Attempt to perform a Web SDK card payment / preAuth / checkCard request where the card scheme used, is not defined in the iFrame configuration object. For example, if AMEX is not defined, use card scheme = AMEX. //An array of card schemes that are accepted by the merchant. //If this field is set, an error will appear if an unsupported card scheme is entered. allowedCardSchemes: ['visa','mastercard'],		For the purpose of this exercise the class is named judopay-errors, and sets a style to be red. You can add any custom style you wish in your .CSS file. <div class="judopay-errors" style="color:red">Error Location</div> For more information, see Step Two: Add the Payment Form to your Website.

Updated 28 Aug 2024

Testing your Web SDK Integration

Testing your Web Payments Integration