> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-uk/p400/how-tos/how-to-process-a-customer-not-present-transaction.md).

# How to Process a Customer Not Present Transaction

Process a Card Not Present (CNP) transaction on a P400 terminal — for purchases, refunds, or account verification when the cardholder isn't present.

{% hint style="info" %}
**Use this when** you need to take a payment, refund, or account verification and the cardholder is not physically present — for example a phone or mail order.
{% endhint %}

{% hint style="warning" %}
**Do NOT use this when** the customer and their card are present at the terminal — use the standard Sale flow instead. Card Not Present is only for transactions where the cardholder isn't physically present, such as phone or mail orders.
{% endhint %}

This guide starts a Card Not Present (CNP) transaction from the Sale screen, where you can take a purchase, refund, or account verification without the physical card.

## Process a Card Not Present transaction

{% stepper %}
{% step %}

### Access the Sale Screen

After logging in, go to the Sale screen.
{% endstep %}

{% step %}

### Open the Menu

Tap the blue banner at the top of the screen.
{% endstep %}

{% step %}

### Select Card Not Present

Choose `Card Not Present` from the menu.
{% endstep %}

{% step %}

### Choose the transaction type

On the next screen, select your preferred CNP method, then choose whether you're processing:

* Purchase
* Refund
* Account Verification
  {% endstep %}
  {% endstepper %}

<details>

<summary>Keywords</summary>

Also called: customer not present, card not present, CNP, MOTO, phone order, mail order, remote payment. Search terms: card not present, CNP, MOTO, phone payment, mail order, account verification.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.verifone.com/support-uk/p400/how-tos/how-to-process-a-customer-not-present-transaction.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.