Testing Voids

testing voids voids cannot be performed on pre authorisations that have been collected (partial or full) card void scenarios (positive flow) important to consider ensure the preauth transactions permission is enabled on your api credentials ensure you have the correct receiptid for the original pre authorisation this is required for you to process the void voids cannot be performed on pre authorisations that have expired, or been collected (partial or full) to simulate voiding a docid\ gwwuvrkwonc5yvk6qhmmi true 237,150,100 unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type unhandled content type request parameters sandbox endpoint https //api sandbox judopay com/transactions/voids http method post header parameters 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 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 void request example { "receiptid" "675014982672486400", "amount" 10 99, "currency" "gbp", "yourpaymentmetadata" { "internallocationref" "example", "internalid" 99 }, "yourpaymentreference" "aa648425 2230 4e4e 8a61 27f06df54542", } response example { "receiptid" "914571470754189312", "originalreceiptid" "914571434016280576", "yourpaymentreference" "e61b5555 31fe 41f3 843a 905a28c552f0", "type" "void", "createdat" "2022 11 28t17 40 31 4741+00 00", "result" "success", "message" "void successful", "judoid" 100502814, "merchantname" "shodan cybersource routing", "appearsonstatementas" "apl /shodancybersourcero", "originalamount" "5 00", "amountcollected" "0 00", "netamount" "5 00", "amount" "5 00", "currency" "gbp", "externalbankresponsecode" "", "carddetails" { "cardlastfour" "1111", "enddate" "1230", "cardtoken" "endper5kpglawedhdj3lzkj5zecqpr4s", "cardtype" 1, "cardscheme" "visa", "cardfunding" "credit", "cardcategory" "", "cardcountry" "us", "bank" "jpmorgan chase bank, n a " }, "consumer" { "yourconsumerreference" "cardswithmultipleconsumers2" } } card void 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 256,103,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 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