Testing CheckCard

testing checkcard these scenarios do not include 3d secure 2 authentication testing see docid\ bdcgiyqdm3mle ubxp1yr for 3d secure 2 authentication testing for your app checkcard scenarios (positive flow) checkcard conducts a zero amount pre authorisation on the consumer's account important to consider zero auth means it does not hold any funds on the customer’s account checkcard tests involve verification of the card cardnumber cardexpirydate cv2 the account is not blocked or blacklisted exists tokenises the card number into an encrypted string a successful checkcard request verifies the card with the issuer and can be authenticated using 3d secure 2, providing you with the confidence the card is valid to make future payments true 220,220,221 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type for more information on api credentials and permissions, see docid\ s 8hoamytkgy13t0p657 test card data to simulate a successful checkcard request use the docid obafnuc1umhk vihhs5d check card request parameters sandbox endpoint https //api sandbox judopay com/transactions/checkcard http method post header parameters depending on how you integrate with judopay, you can authenticate requests by /paymentsession , or tokensecretauth the token and secret pair for more information, see docid\ ylkw5coh5nqnfq3j wjk2 265,403 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type body parameters configuration property descriptions true 243 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type check card request example { "cardnumber" 4111111111111111, "cv2" 123, "expirydate" "12/30", "cardaddress" { "address1" "cardholder house", "address2" "1 cardholder street", "town" "cardholder town", "postcode" "ab1 2cd", "countrycode" 826 }, "judoid" 100100100, "yourconsumerreference" "2b45fd3f cee5 4e7e 874f 28051db65408", "yourpaymentreference" "6482c678 cad3 4efd b081 aeae7a89a134", "cardholdername" "john doe", "mobilenumber" 7999999999, "phonecountrycode" 44, "emailaddress" "test user\@judopay com", "shippingaddress" { "isbillingaddress" true }, "threedsecure" { "authenticationsource" "browser", "methodnotificationurl" "https //api sandbox judopay com/order/3ds/methodnotification", "challengenotificationurl" "https //api sandbox judopay com/order/3ds/challengenotification", "methodcompletion" false } } response example { "receiptid" "915607863668412416", "yourpaymentreference" "cd6fcd20 9c0a 436c 9ec8 2caee5324e6a", "type" "checkcard", "createdat" "2022 12 01t14 18 46 5375+00 00", "result" "success", "message" "authcode 0", "judoid" 100502814, "merchantname" "shodan cybersource routing", "appearsonstatementas" "apl /shodancybersourcero", "originalamount" "0 00", "netamount" "0 00", "amount" "0 00", "currency" "gbp", "externalbankresponsecode" "0", "authcode" "0", "paymentnetworktransactionid" "123456789012345", "carddetails" { "cardlastfour" "1111", "enddate" "1230", "cardtoken" "oalxtkjeig9mjttenupfngnzog62ryt9", "cardtype" 1, "cardscheme" "visa", "cardfunding" "credit", "cardcategory" "", "cardcountry" "us", "bank" "jpmorgan chase bank, n a " }, "billingaddress" { "postcode" "tr14 8pa" }, "consumer" { "yourconsumerreference" "cv2 test" }, "device" { "identifier" "bd9b254a156847e9a73f54929c465701" }, "threedsecure" { "attempted" false }, "risks" { "postcodecheck" "unknown", "cv2check" "passed", "merchantsuggestion" "allow" } } checkcard 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 true 239,117,100 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type where the codes remain fixed, the descriptions may change you should not build any error handling logic based on these descriptions for a list of possible error codes, types and descriptions, see docid zrsihomuew xnrq4pbtj