Virtual Terminal (MOTO)

what is a virtual terminal? virtual terminals offer an alternative way of processing transactions when traditional payment (pos) terminals are not available these are also known as mail order telephone order transactions ( moto ) this web based payment system enables your customer support agents to manually input the transaction and payment information remotely on your consumer's behalf, over the telephone or via email moto transactions via a virtual terminal do not follow the 3d secure 2 payment flow there is a higher fraud risk associated with this taking a payment via the virtual terminal using the judopay portal you can accept moto transactions via our virtual terminal screen from the judopay portal from the side menu, select v terminal the virtual terminal screen appears enter the following details location if you have access to more than one judoid , you will see a location drop down list made up of the judoid + truncated trading name select the location based on the judoid from the selected judoid, the form will automatically update \ currency depending on enabled ecom routes \ extra fields if mcc = 6012 / 6051 / 7299 order id this is your unique order identification / reference currency the available currency options in the dropdown list are defined when setting up your judopay account please contact judopay if you need additional currencies for your transaction amount format two decimal places if you are looking to process currencies that use a different structure than two decimal places, please contact judopay for support click the continue button the payment screen appears enter the consumer's card details click the confirm payment button the payment successful screen appears successfully completed transactions will be available to view in the history section of the judopay portal account funding transactions if your account is not configured for aft, the virtual terminal flow remains unchanged account funding transactions (aft) are required for merchants operating in specific money movement and financial services categories , as defined by card schemes for these merchants, additional data must be included in payment requests to ensure transactions are processed in line with scheme and acquirer requirements failure to provide the required aft fields docid 5ol ptsgbhvgkwjwd0ghg may result in transactions being declined, flagged, or subject to additional scrutiny important to consider aft requirements apply only to merchants with supported mccs for more information, see applicable merchants docid 5ol ptsgbhvgkwjwd0ghg these requirements are defined by the card schemes and acquirers , and apply across all supported gateways missing or invalid aft data may result in transaction declines validation errors acquirer flags to submit aft data, merchants must upgrade to judopay's transaction api version 6 25 or higher for more information, see transaction api https //docs judopay com/api reference/api reference taking a payment with aft data the account funding information section is displayed only for merchants configured with supported mccs for more information, see applicable merchants docid 5ol ptsgbhvgkwjwd0ghg if your account is not configured for aft, this section will not appear and the virtual terminal flow remains unchanged from the judopay portal from the side menu, select v terminal the virtual terminal screen appears the aft recipient information section is also displayed for merchants configured with supported mccs enter the following details location if you have access to more than one judoid , you will see a location drop down list made up of the judoid + truncated trading name select the location based on the judoid from the selected judoid, the form will automatically update \ currency depending on enabled ecom routes \ extra fields if mcc = 6012 / 6051 / 7299 order id this is your unique order identification / reference currency the available currency options in the dropdown list are defined when setting up your judopay account please contact judopay if you need additional currencies for your transaction amount format two decimal places if you are looking to process currencies that use a different structure than two decimal places, please contact judopay for support aft recipient information section enter the following details first name recipient's first name address line 1 recipient's address country code recipient's country format iso alpha 2 state required only for us & canada account id recipient's account identifier business application id indicates the purpose of the transaction select from the following values aa – account to account fd – funds disbursement ft – funds transfer pd – payroll tu – top up wt – digital wallet account type indicates the recipient's account type select from the following values 00 other 01 trn & ban 02 iban 03 card (first6 & last4) 06 ban & bic (swift code) click the continue button the billing information screen appears note this screen is optional and will appear for merchants configured with supported aft mccs, to display the billing address fields required for the additional recipient information and if the billing address information has not already been provided enter the consumer's billing information email country mobile number address line city postal code click the continue button the pay with card screen appears enter the consumer's card details click the confirm payment button the payment successful screen appears if you are unsure which business application id or account type values should be used for your transaction, contact your acquirer validation rules for any missing or invalid information inline validation messages will be displayed if no aft fields are completed, the payment proceeds normally if any aft field is populated all required aft fields must also be completed partial aft field submissions are not supported business application id and account type must be valid supported values some business application id and account type combinations may not be allowed your acquirer is responsible for confirming the appropriate configuration for your transaction scenarios partial submissions are not allowed for the purpose of this exercise, the first name field has been completed, leaving the remaining aft fields empty, which will cause a validation error