Testing Collections

testing collections these scenarios do not include 3d secure 2 authentication testing see docid\ bdcgiyqdm3mle ubxp1yr for 3d secure 2 authentication testing for your app card collections scenarios (positive flow) collect funds previously reserved using the docid\ gwwuvrkwonc5yvk6qhmmi request important to consider ensure you have the correct receiptid for the original pre authorisation this is required for you to process the collection the expiry time of the reserved pre authorised funds differs across acquirers if not collected, the reserved funds are released and the collection request will be declined to request the funds, attempt a /transactions/payments request instead you can collect partial amounts or multiple partial amounts, as long as they do not exceed the amount of the original pre authorisation ensure the currency in the collection request matches the currency from the original pre authorisation to simulate collecting a docid\ gwwuvrkwonc5yvk6qhmmi 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 request parameters sandbox endpoint https //api sandbox judopay com/transactions/collections http method post 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 collection request example { "receiptid" "675014982672486400", "amount" 10 99, "currency" "gbp", "yourpaymentmetadata" { "internallocationref" "example", "internalid" 99 }, "yourpaymentreference" "aa648425 2230 4e4e 8a61 27f06df54542", } response example { "receiptid" "937657990037798912", "originalreceiptid" "937657941614559232", "yourpaymentreference" "aa648425 2230 4e4e 8a61 27f06df54542", "type" "collection", "createdat" "2023 01 31t10 38 05 6451+00 00", "result" "success", "message" "authcode ", "judoid" 100042597, "merchantname" "shodan ai routing", "appearsonstatementas" "apl /shodanairouting ", "originalamount" "10 99", "netamount" "10 99", "amount" "10 99", "currency" "gbp", "acquirertransactionid" "64012420784005660136", "externalbankresponsecode" "", "authcode" "574623", "carddetails" { "cardlastfour" "3436", "enddate" "1230", "cardtoken" "sof km2rtbuvrp2nwvrbwsvjoq", "cardtype" 11, "cardscheme" "visa", "cardfunding" "debit", "cardcategory" "", "cardcountry" "fr", "bank" "credit industreil et commercial" }, "consumer" { "yourconsumerreference" "collection test" }, "threedsecure" { "attempted" false } } card collections 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 268,111,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