---
title: Virtual Terminal (MOTO)
slug: virtual-terminal-moto
docTags: 
createdAt: 2025-03-11T10:19:19.793Z
---

# 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.

:::hint{type="warning"}
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.

::Image[]{src="https://api.archbee.com/api/optimize/QGXTyW3MgdNcMjdEa0v8r/rRjNb-g3aLbrJvA80YJtf-20260511-133123.png" size="58" width="679" height="724" position="center" alt="virtual terminal" darkWidth="679" darkHeight="724" showCaption="false"}

**From the Judopay Portal**:

::::WorkflowBlock
:::WorkflowBlockItem
From the side menu, select **V-terminal**.
:::

:::WorkflowBlockItem
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.**
:::

:::WorkflowBlockItem
Click the **Continue **button.
:::

:::WorkflowBlockItem
The **payment screen** appears.
Enter the consumer's card details.
:::

:::WorkflowBlockItem
Click the **Confirm Payment** button.
:::

:::WorkflowBlockItem
The **Payment successful** screen appears.
:::
::::

Successfully completed transactions will be available to view in the **History **section of the Judopay Portal.

***

# Account Funding Transactions

:::hint{type="info"}
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)

:::hint{type="info"}
If your account is **not **configured for AFT, this section will not appear and the Virtual Terminal flow remains unchanged.
:::

::Image[]{src="https://api.archbee.com/api/optimize/QGXTyW3MgdNcMjdEa0v8r/tMuSX7yV5_D6ghsD8s_RQ_aft-vt-1.png" size="70" isUploading="false" position="center" width="785" height="1271" darkWidth="785" darkHeight="1271" alt="aft virtual terminal" showCaption="false"}

**From the Judopay Portal**:

::::WorkflowBlock
:::WorkflowBlockItem
From the side menu, select **V-terminal.**
:::

:::WorkflowBlockItem
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.**


:::

:::WorkflowBlockItem
**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)
:::

:::WorkflowBlockItem
Click the **Continue **button.
:::

:::WorkflowBlockItem
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.
:::

:::WorkflowBlockItem
The **Pay with card screen** appears.
Enter the consumer's card details.
:::

:::WorkflowBlockItem
Click the **Confirm Payment** button.
:::

:::WorkflowBlockItem
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.

:::hint{type="warning"}
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:*

::Image[]{src="https://api.archbee.com/api/optimize/QGXTyW3MgdNcMjdEa0v8r/q7SlQsCbGJmKdyQPigb4N-20260511-094300.png" size="56" width="525" height="312" position="center" alt="vt validation rules" darkWidth="525" darkHeight="312" showCaption="false"}