Introduction

welcome to judopay accept simple and secure payments in your app or website with judopay’s sdks quickly capture your customer’s card details for immediate payments or save them securely for future payments to get started then, you will receive access to your judopay dashboard and the sandbox environment there is a due diligence process to complete before you go live, so please speak to a member of the team before doing any development work to follow the steps to quickly integrate and produce a test card payment using judopay’s web sdk, see docid\ uuvcdjxtcajyqhd4xfpye important to consider when integrating your app when to have multiple judoids you can have one judoid multiple judoids a judoid can be allocated for a route or location basis multiple judoids can also be created to take into account a more granular set of transaction reporting, for example to separate online transactions, the location where transactions took place, or the most used payment method all judoid's can have different configurations enabled permissions you will receive your api credentials when setting up your account with judopay these credentials control the permissions enabled on your sandbox and live token and secret pair(s) each token and secret pair will have specific permissions configured the following illustration provides a helpful overview on the permissions that need to be set up, in order for each step in the payment flow to be able to take place the following illustration provides a helpful overview on the permissions that need to be set up, in order for each step in the payment flow to be able to take place permissions flow diagram possible configuration examples depending on the payment methods, currencies and card schemes you want to accept, you can configure these specifically, (for example visa, mastercard, apple pay, card, paypal), or set to accept all check your judoids and tokens are configured and enabled as appropriate if you want to include amex , contact mailto\ help\@judopay com to set this up amex is not automatically added and requires a separate configuration payment methods transaction medium (ecom / moto) currencies card schemes transaction types block payments from a specific region using our transaction api interact with our docid\ bcxnm5keok nlnrztafut in the following ways select your integration version see the authentication methods available how to create a /paymentsession authenticate all requests or a specific request manually test a request view example success and error responses for more information, see docid\ apyeqdsycdrkuxggnlhup authentication methods in online and mobile payments, security is a number one concern authentication and verification of the identity of the cardholder is important for preventing fraudulent transactions and refunds each request to judopay’s transaction api requires authentication depending on how you integrate with judopay, the following methods are recommended to authenticate requests using our docid 40dwe6lbub7vdkza1qydc /paymentsession calling directly to our docid\ bcxnm5keok nlnrztafut /paymentsession , or tokensecretauth the token and secret pair for more information, see docid\ ylkw5coh5nqnfq3j wjk2 testing your integration prior to testing prerequisites make sure you have the following set up prior to testing you are using sandbox tokens in the sandbox environment you are using test cards in the sandbox environment your judoids and tokens are configured and enabled as appropriate you need your https //www judopay com/apply sandbox account so you can process test transactions while developing your app sandbox environment the purpose of the sandbox environment is to allow you to test and replicate various use cases, payment flows and scenarios that your app should support use the docid obafnuc1umhk vihhs5d and data to test your integration is working correctly this will give you confidence that all is working as expected when your integration goes live direct api integration scenarios (card payments) docid\ bdcgiyqdm3mle ubxp1yr docid\ nq7c98panemfgukhbpucb docid\ gwwuvrkwonc5yvk6qhmmi docid\ mebkvlfmxdp3kolys0uda docid\ yvjgzt2gxwbdxm3m0wemu docid\ dmbakskjll551suxqipum docid\ n6bow dlqrqo olwrjvfk docid 3ssysze0atrwujrqsiqov docid\ gb1c oqbh7uuw8rzusawt docid\ zia7tb a4kybkm0v4okjy for more information see, docid 6bahfduikw3xms1pv8oex web payments integration scenarios (card payments) docid\ zv5mpxmmqxjq1rp3fayxk docid\ zv5mpxmmqxjq1rp3fayxk docid\ zv5mpxmmqxjq1rp3fayxk for more information see, docid\ zv5mpxmmqxjq1rp3fayxk mobile sdk integration scenarios (card payments) docid\ vzb3q7wp2hf0ljgdo8vnd docid 9t9c80adjpmu0baiys7sk for more information see, docid\ gvthuybg kbet2sxnynlo web sdk integration scenarios (card payments) docid\ a33b4pwt6brofejpghdh2 docid\ a33b4pwt6brofejpghdh2 docid\ a33b4pwt6brofejpghdh2 docid\ a33b4pwt6brofejpghdh2 docid\ a33b4pwt6brofejpghdh2 for more information see, docid\ a33b4pwt6brofejpghdh2 wallet payment scenarios (via direct api integration) docid\ hq1tyqlikepvzyqlw l07 docid\ hq1tyqlikepvzyqlw l07 for more information see, docid\ hq1tyqlikepvzyqlw l07 wallet payment scenarios (via web sdk integration) docid\ t13itu 7qx7ylrxgvj5jt docid\ t13itu 7qx7ylrxgvj5jt for more information see, docid\ t13itu 7qx7ylrxgvj5jt wallet payment scenarios (via mobile sdk integration) docid\ hyanzim115id6dabs bkp docid\ pdwr34avmt3iws1j8xtsq for more information see, docid\ iyacwlidscqikmcfrrkhp key terms familiarise yourself with the key terms we use, to help you with your integration judoid the judoid is a unique id supplied by judopay, which you add to the request body of each transaction request string of numbers maximum length 9 characters format 100100100 do not include spaces or dashes api credentials you will receive your api credentials when setting up your account with judopay these credentials control the permissions enabled on your sandbox and live token and secret pair(s) each token and secret pair will have specific permissions configured for more information, see docid\ s 8hoamytkgy13t0p657 3d secure 2 we support all versions of the 3d secure protocol up to and including version 3ds2 2 3d secure 2 0 aims to improve the security and consumer experience, including helping merchants achieve strong customer authentication (sca) compliance under psd2 the payment services directive (psd2), has introduced a new regulatory requirement strong customer authentication (sca) the aim of the sca is to add an increased layer of security for card not present transactions, when making mobile and online payments make sure your account has 3d secure 2 api credentials enabled contact ​customer support​​ to set this up in the 3d secure 2 payment flow, the issuer will make a decision on whether they have enough authentication data to proceed with the transaction, or if they require the cardholder to further authenticate the transaction with additional strong customer authentication (sca) checks for more information, see docid 0yqdp4kpyoijj6unudn9f to authenticate the transaction, merchants can verify the consumer's identity with the issuer to be compliant with sca, 3d secure 2 transactions have additional authentication and transaction information within the payment flow for more information on 3d secure 2, see docid\ wpfmf662qaigegrpu mow merchant initiated transactions merchant initiated transactions (mit)s, for example subscription type payments unscheduled transactions tips increase in taxi fares for more information, see docid\ ek1dldo8cgr9di226zlyf mits are also impacted by sca you need to tag your mit / recurring transactions correctly to ensure your transactions are not declined by your customers’ issuing bank card token payments use the card token in the request body, instead of the card number the card token is a randomly generated string linked to a card saved securely within the judopay card vault you will not take on additional pci scope, as the card token does not have any sensitive card information, so it can be stored in your database alternative payments alternative payment methods refers to a range of payment methods beyond the traditional ways of paying with cards and cash currently judopay accepts the following alternative payment methods docid 44rrma0krzsqsvnri7qbw docid\ rcuemk4qqk m ndm0nh8g (beta) (beta) wallet payments integrate apple pay™ and google pay™ via web and mobile for more information, see docid\ xugwb4y6tqksmz quyccz web payments a minimal integration is all that is required to enable you to take a payment generate hosted payment page links using judopay’s transaction api and redirect the consumer back to your own website, using configured redirect urls this helps minimise your pci scope by providing consumers with a secure way to pay online via their browser, optimised for any device for more information, see docid\ glorwwwfkfqp34fykcxe8 sdks judopay’s sdks enables merchants to easily integrate and customise a seamless consumer checkout experience, for mobile, web and server integrations all of our sdks come built in with the following features secure customer authentication (sca) compliance 3d secure fraud prevention tools supports alternative payment methods you will not take on additional pci scope, as sensitive card information is submitted by consumers into fields hosted by judopay, encrypted and transmitted on behalf of the merchant, meaning it does not touch the merchant’s server if you prefer to use your own ui for the consumer’s checkout journey, you can still easily integrate with judopay using only a few lines of code to begin accepting payments for more information, see docid\ fyef n37tnl1c5dsscml3 docid 40dwe6lbub7vdkza1qydc docid\ mzcnx mb0nespjb4mjpz4