Testing Card PreAuths

testing card preauths these scenarios do not include 3d secure 2 authentication testing see testing 3d secure 2 authentication docid\ bdcgiyqdm3mle ubxp1yr for 3d secure 2 authentication testing for your app card preauth and card token preauth scenarios (positive flow) important to consider yourpaymentreference is your unique reference for each transaction when making token preauths, yourconsumerreference must match the original reference when the token was initially created true false 272,130false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type for more information on api credentials and permissions, see introduction docid\ s 8hoamytkgy13t0p657 test card data to simulate a successful preauth use the test cards docid obafnuc1umhk vihhs5d card preauth and card token preauth request parameters sandbox endpoint https //api sandbox judopay com/transactions/preauths 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 authentication methods docid\ ylkw5coh5nqnfq3j wjk2 false false 265,403false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type body parameters configuration property descriptions true false 243false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type card preauth request example { "cardnumber" 4111111111111111, "cv2" 123, "expirydate" "01/25", "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", "yourpaymentmetadata" { "internallocationref" "example", "internalid" 99 }, "amount" 1 01, "currency" "gbp", "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, "challengerequestindicator" "challengeasmandate" } } card token preauth request example { "yourconsumerreference" "2b45fd3f cee5 4e7e 874f 28051db65408", "yourpaymentreference" "34a73594 f3b2 414c a5c9 58679530b418", "judoid" 100502814, "amount" 5 00, "cardtoken" "sof xfmzmenor sj9mtrcvrxhw", "cv2" "838" } response example { "receiptid" "914568453493526528", "yourpaymentreference" "34a73594 f3b2 414c a5c9 58679530b418", "type" "preauth", "createdat" "2022 11 28t17 28 32 0996+00 00", "result" "success", "message" "authcode 5", "judoid" 100502814, "merchantname" "shodan cybersource routing", "appearsonstatementas" "apl /shodancybersourcero", "originalamount" "5 00", "netamount" "5 00", "amount" "5 00", "currency" "gbp", "acquirertransactionid" "7016984508", "externalbankresponsecode" "0", "authcode" "5", "carddetails" { "cardlastfour" "1111", "enddate" "1222", "cardtoken" "oalxtkjeig9mjttenupfngnzog62ryt9", "cardtype" 1, "cardscheme" "visa", "cardfunding" "credit", "cardcategory" "", "cardcountry" "us", "bank" "jpmorgan chase bank, n a " }, "billingaddress" { "address1" "32 edward street", "address2" "camborne", "town" "cornwall cowrnwall", "postcode" "tr14 8pa", "countrycode" 426 }, "consumer" { "yourconsumerreference" "cv2 test" }, "risks" { "postcodecheck" "unknown", "cv2check" "unknown", "merchantsuggestion" "allow" } } if your request was successful, you will receive a code 200 and a receiptid a receiptid is judopay's unique reference for the transaction it is used to process refunds or cancellations and to help us investigate any issues with the transaction card preauth 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 to simulate an unsuccessful flow , use the following test card details true false 80,96,108,83,84,81false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type follow our suggested guidelines to simulate negative scenarios, to test your app’s error handling true false 254,150false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false 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, seesee codes and descriptions docid zrsihomuew xnrq4pbtj next steps using the successful preauth test transactions, you can test the following scenarios testing voids docid\ dmbakskjll551suxqipum testing collections docid\ yvjgzt2gxwbdxm3m0wemu