Update<\/strong>\u00a0to update the information for an existing user.<\/li>\n<\/ol>\nForced logout after inactivity<\/h2>\n
The session ends after 15 minutes of inactivity, and the users need to enter their login details, except for the account name. This is a PCI requirement.\u00a0<\/p>","url":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/skin\/moto-feature","articleFields":{"parameters":{"parent_page":"classic Hosted Payment Pages (HPP)","new_desc":"looking for a POS integration for MOTO transactions"},"sitemap":{"priority":0.3},"id":"24217149","type":"page","_expandable":{"operations":""},"status":"current","feedback_component":true},"algolia":{"url":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/skin\/moto-feature","title":"MOTO Feature","content":"Using Adyen's\u00a0Mail Order \/ Telephone Order (MOTO) your shopper can make a call to a call center or send a coupon\/voucher to communicate their credit card number initiating an authorisation process handled by your team.\u00a0\nWith Adyen's MOTO features, you can integrate your webshop payments with your call center payments, and enjoy unified reporting covering both transaction flows.\nBy default, Adyen merchant accounts are set up for ecommerce for contractual reasons.\nRequirements\nTo process MOTO transactions, you need a dedicated Adyen merchant account under your company account, besides your ecommerce merchant account. The extra account is necessary because MOTO and ecommerce traffic flows are different,\u00a0and therefore\u00a0they require ad-hoc handling of operations and processes like flagging, supported payment methods or fraud control.\nThese are the basic requirements to enable MOTO:\n\nSeparate merchant account to handle MOTO traffic.\u00a0\nAdditional user permissions.\nLink to the call center application.\n(Optional) Dedicated skin for the call center application.\nEnable the Call Center user role in your merchant account or create a separate\u00a0user account with\u00a0Call Center user role\u00a0rights to use the call center.\n\nRequesting a MOTO account\nPerform the following steps to request a MOTO account.\n\nLogin to\u00a0Customer Area.\nSelect\u00a0Account\u00a0>\u00a0Merchant accounts.\nSelect\u00a0Request new merchant accountt\u00a0and\u00a0proceed to create an\u00a0Ecommerce\u00a0account.\nIn the account set-up field\u00a0Reason for requesting this account, add \"MOTO transactions\" as a remark.\n\nOnce the request for your MOTO account is completed, Adyen will contact you about the status of your account.\nInterfaces and integration\nYou can accept MOTO transactions by using Adyen's Hosted Call Center Interface, available to all MOTO merchant accounts. This interface is similar to\u00a0Adyen's Hosted Payment Pages (HPP)\u00a0for ecommerce; the hosted call center interface functionality is extended to include basic call center features to allow your call centre representatives to log on and manually key in orders they receive via mail or phone.\nYou can modify the look and feel of this application by\u00a0uploading a skin. Normally, this is the most efficient way to integrate.\nPayment methods\nThe following payment methods are currently available for MOTO:\n\nCredit cards\nSEPA Direct Debit\n\n 3D Secure authentication for credit cards is not available in the MOTO flow. \nAdyen Hosted Call Center interface\nYou can reach the call center interface by following these URLs:\n\n\n\n\n\n\n\n\n\nTest call center\nhttps:\/\/callcenter-test.adyen.com\/callcenter\/action\/login.shtml\n\n\nLive call center\nhttps:\/\/callcenter-live.adyen.com\/callcenter\/action\/login.shtml\n\n\n\nMake a call center transaction\n\nLog in to the call center interface.\nWhen you visit the URL, you see the familiar Adyen login page.\nYour employees should log on using your\u00a0company account\u00a0code. Only specific users should have access to this interface i.e. call center representatives and administrative roles.\nEnter order details.\nAfter a successful login, the following screen prompts the call center agent to enter the following information:\n\nMerchant Account: the merchant account to use for this payment. If a user is assigned to one merchant account only, this field is not shown.\nCurrency \/ Amount: the specified payment amount, with a decimal separator.\nFor example, enter\u00a0100.00\u00a0for an amount of EUR 100.00.\nJapanese yen does not take minor units (For example, enter\u00a01001\u00a0to specify an amount of 1001 yen).\nCurrency options are available in a drop-down list that includes only the configured currencies for the selected merchant account.\nPayment Reference\u00a0the (merchant) reference for the payment.\nA reference to uniquely identify the payment.\u00a0This reference is used in all communication with you about the payment status.\u00a0We recommend using a unique value per payment; however, it is not a requirement.\n\n\nIf you need to provide multiple references for a transaction, you can enter them in this field.\u00a0Separate each reference value with a hyphen character (\"-\").\nThis field has a length restriction: you can enter max. 80 characters.\n\nCountry Code: by default, the payment methods offered to the shopper are filtered based on the location of the shopper's IP address.\nFor example, this prevents displaying a German payment method to a UK shopper.\nThis IP-to-country mapping is not 100% accurate; if you have already defined the country\/region of the shopper, you may want to set it explicitly.\nShopper Reference:\u00a0a unique identifier for the shopper.\nFor example, a customer ID in a shopping cart system.\nVelocity fraud checks use this field.\nThis field is mandatory if the\u00a0Store these details for recurring transactions\u00a0checkbox is selected.\nEmail Address: the email address of the shopper. This field\u00a0is mandatory if the\u00a0Store these details for recurring transactions\u00a0checkbox is selected.\n\nStore these details for recurring transactions: If you select this checkbox, we store the payment details for\u00a0recurring payments.\nBy default, the checkbox is selected.\nWhen the checkbox is selected, the\u00a0Shopper Reference\u00a0and\u00a0Email Address\u00a0fields become mandatory.\nAirline data fields are shown when applicable.\u00a0\nThe information on this page can either be typed in manually\u00a0or automatically fed from another application, such as your internal ordering system (if it is web-based).\n\n\nPayment pages\nAfter you select Submit, the payment method page opens. The available payment methods appear on this page, as well as other parameters like currency, amount, and country\/region, depending on your configuration.\nDepending on the selected payment method, the regular payment screens are shown. The call center agent can enter the payment details here, as instructed by the customer on the phone.\n\nTo display appropriate payment methods as per the devices,\u00a0create a skin and select display only the appropriate payment methods.\n\nPayment success or failure page\nAfter a successful payment, the Adyen-hosted success page appears. And in the case of any errors occur, the failure page appear.\nIn the Customer Area,\u00a0you can retrieve a payment overview, payment status, and payment details, as well as the MOTO user who submitted the payment.\nThe submit author is shown on the payment detail page, in the row whose\u00a0Item\u00a0column value sets to\u00a0Payment, under the\u00a0Created By\u00a0column.\nExtra request parameters\nYou can add extra parameters to the call center URL:\n\n\nshopperLocale: A combination of a\u00a0language code and country code to specify the language used in the session.\nshopperLocale = language code + _ + country code\nFor example,\u00a0en_GB\u00a0stands for British English.\nWhen a country\/region specification is not required, use only the language code. For example,\u00a0fr, not\u00a0fr_FR, for France.\nBy default, the shopper locale is en_GB.\nThis value is forwarded to the first subsequent payment request.\n\n\ncurrencyCode: Defines the default currency for the transaction.\u00a0The three-character ISO currency code.\n\n\npaymentAmount:\u00a0The payable amount that can be charged for the transaction, in minor units.\nThe transaction amount needs to be represented in minor units according to the Currency codes table. Some currencies do not have decimal points, such as JPY, and some have 3 decimal points, such as BHD.\nFor example, GBP 10 is submitted as 1000, whereas JPY 10 is submitted as 10.\nThe paymentAmount field\u00a0is used\u00a0if you set currencyCode.\n\n\ncurrencies: A comma-separated list of the currencies that need to be available in the currency selection drop-down list.\nFor example:\u00a0currencies=EUR, GBP.\nOnly the supported currencies in the\u00a0currencies\u00a0parameter are shown.\nFor example, you have not configured your account for USD currency is not shown even if you include it as a value in the\u00a0currencies\u00a0parameter.\nThis value is also forwarded to the first subsequent payment request.\n\n\nCall center skin\nWhen you launch the call center application for the first time, a default\u00a0skin\u00a0is applied. You can override this setting by uploading your skin. This is the same process as with ecommerce transactions. If you do not upload a skin, HPP uses the Adyen default skin.\nIn the Customer Area, define a\u00a0Call Center Skin Code\u00a0in the merchant settings page of the merchant account: go to\u00a0Account\u00a0> Merchant Settings:\u00a0\nTheResult URL and the Continue-to URL\u00a0of the call center application should be set as follows:\n\n\n\n\n\n\n\n\n\nResult URL for Test\nhttps:\/\/callcenter-test.adyen.com\/callcenter\/action\/result.shtml\n\n\nContinue-to-URL for Test\nhttps:\/\/callcenter-test.adyen.com\/callcenter\/action\/callcenter.shtml\n\n\nResult URL for Live\nhttps:\/\/callcenter-live.adyen.com\/callcenter\/action\/result.shtml\n\n\nContinue-to-URL for Live\nhttps:\/\/callcenter-live.adyen.com\/callcenter\/action\/callcenter.shtml\n\n\n\nThese settings make sure that the operator stays in the call center application after processing a transaction.\nThe call center interface uses the hosted payment pages (HPP), so you can benefit from their feature set.\nYou can set the\u00a0Skin\u00a0skin option if you plan to capture airline data.\nCredentials for a call center\nYou need at least one user with CallCenter user role rights and permissions. We recommend creating specific accounts for each call center agent. This way you can control access per employee and keep track of activities in the audit trail. You can find the audit trail in the Customer Area\u00a0>\u00a0Account\u00a0> Audit Trail.\nTo assign a CallCenter user role:\n\nGo to\u00a0Customer Area\u00a0>\u00a0Account\u00a0>\u00a0Users.\nClick the\u00a0New\u00a0tab to add a new user, or click on an existing username.\nOn the Roles tab, enable the\u00a0CallCenter user role\u00a0by turning on a toggle next to it.\nOn the Accounts tab,\u00a0assign the relevant MOTO accounts by turning on corresponding toggles.\nClick the\u00a0Save\u00a0button to create the user or\u00a0Update\u00a0to update the information for an existing user.\n\nForced logout after inactivity\nThe session ends after 15 minutes of inactivity, and the users need to enter their login details, except for the account name. This is a PCI requirement.\u00a0","type":"page","locale":"pt","boost":15,"hierarchy":{"lvl0":"Home","lvl1":"Online payments","lvl2":"Classic integrations for Ecommerce","lvl3":"Hosted Payment Pages","lvl4":"Skins for Hosted Payment Pages","lvl5":"MOTO Feature"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/pt","lvl1":"https:\/\/docs.adyen.com\/pt\/online-payments","lvl2":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations","lvl3":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages","lvl4":"https:\/\/docs.adyen.com\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/skin","lvl5":"\/pt\/online-payments\/classic-integrations\/hosted-payment-pages\/skin\/moto-feature"},"levels":6,"category":"Online Payments","category_color":"green","tags":["Feature"]}}