> For the complete documentation index, see [llms.txt](https://help.jupico.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.jupico.com/transactions/running-a-sale-for-an-existing-customer.md).

# Running a 'Sale' for an existing customer

## Performing a 'Sale' transaction for an existing customer (card on file) <a href="#performing_a_sale_transaction_for_an_existing_customer_card_on_file" id="performing_a_sale_transaction_for_an_existing_customer_card_on_file"></a>

* Step 1 -> [Login](https://accounts.jupico.com/payments/login)
* Step 2 -> Click **Customers** on the left hand navigation menu
* Step 3 -> Use search bar at the top to locate your Customer.

{% hint style="info" %}
You can search for your customer by name, last 4 of credit card number, phone, or email.
{% endhint %}

* Step 4 -> Once the Customer is found, navigate to the right side of the screen and click on the credit card icon. This will open up the sale window for this Customer with their "Default" card.
* Step 5 -> Enter Sale amount and all other required fields.

{% hint style="info" %}
If you enter an email address, the receipt will be automatically delivered to that email.
{% endhint %}

* Step 6 -> Click "Charge"
* Step 7 -> If the transaction was processed, you will see "Transaction Successful".

{% embed url="<https://www.youtube.com/watch?v=K-IFr9fQABs>" %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.jupico.com/transactions/running-a-sale-for-an-existing-customer.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.