Transaction API Reference

judopay’s transaction api reference documentation provides information on the available endpoints all examples within the judopay documentation use the sandbox environment so you can process test transactions while developing your app important fields before you get started, note the key fields that need to be sent between your app and judopay when making payments judo id specific to a merchant or location you wish to pay string of numbers maximum length 9 characters format 100100100 do not include spaces or dashes your consumer reference allows you to uniquely identify your customer must be supplied in a payment request can be used to help merchants to reconcile can be used to prevent fraud from occurring through the system all subsequent transactions must exactly match the consumer reference as it is case sensitive your payment reference your reference for a payment should be unique to protect your customers against duplicate transactions all subsequent transactions must exactly match the payment reference as it is case sensitive for more information, see introduction docid\ s 8hoamytkgy13t0p657 for more information on how to use our transaction api, see interact with the transaction api docid\ apyeqdsycdrkuxggnlhup view our api change logs docid\ opwju7rmaxcdj6bkimg35