Testing SaveCard

testing savecard these scenarios do not include 3d secure 2 authentication testing see docid\ bdcgiyqdm3mle ubxp1yr for 3d secure 2 authentication testing for your app savecard scenarios (positive flow) use savecard if you do not want to perform a pre authorisation check on a customer's account savecard stores the card details and tokenises the card number into an encrypted string during the savecard request flow, judopay validates the fields in the request model before storing the card details and tokenising the card number if the request fails these checks, for example due to an incorrect field value, or the field has been incorrectly formatted, you will receive a model error response for more information, see docid zrsihomuew xnrq4pbtj the cardtoken is not validated by the issuer, until it is used in a payment or preauth request important to consider savecard involves storing the following card details cardnumber cardexpirydate cv2 tokenises the card number into an encrypted string the savecard request is not processed through the 3d secure 2 flow and is not authenticated for a request to follow the 3d secure 2 authentication flow, use docid 3ssysze0atrwujrqsiqov instead you cannot use the receiptid from the savecard response for merchant initiated transactions this is due to the savecard request not being validated by the issuer for more information on the merchant initiated transaction flow, see docid\ gb1c oqbh7uuw8rzusawt savecard does not validate the card or account, as the request does not go to the payment gateway 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 savecard request use the docid obafnuc1umhk vihhs5d savecard request parameters sandbox endpoint https //api sandbox judopay com/transactions/savecard 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 210,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 savecard request example { "cardnumber" "4976000000003436", "expirydate" "12/30", "cv2" "452", "yourconsumerreference" "carlie1656\@example com", "cardholdername" "brenda quigley", "judoid" "100078697" } response example { "receiptid" "9551393333331152", "yourpaymentreference" "judo registercard 638149261737657931", "type" "save", "createdat" "2023 03 20t16 22 53 7970+00 00", "result" "success", "message" "register card", "judoid" 100042597, "merchantname" "shodan ai routing", "appearsonstatementas" "apl /shodanairouting ", "originalamount" "0 00", "netamount" "0 00", "amount" "0 00", "currency" "gbp", "acquirertransactionid" "123456", "externalbankresponsecode" "", "authcode" "", "carddetails" { "cardlastfour" "3436", "enddate" "1230", "cardtoken" "sof obcph1avsugsj8uf9wnt7a", "cardtype" 11, "cardscheme" "visa", "cardfunding" "debit", "cardcategory" "classic", "cardcountry" "fr", "bank" "credit industriel et commercial", "cardholdername" "brenda quigley" }, "consumer" { "yourconsumerreference" "carlie1656\@example com", }, "threedsecure" { "attempted" false }, "risks" { "postcodecheck" "unknown", "cv2check" "passed", "merchantsuggestion" "allow" } } savecard scenarios (negative flow) field and formatting errors can occur for various reasons, it can be impossible to simulate all the model errors 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 model errors, to test your app’s error handling true 187,88,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 next steps using the cardtoken from the savecard response, you can test the following scenarios docid\ gwwuvrkwonc5yvk6qhmmi docid\ nq7c98panemfgukhbpucb