> For the complete documentation index, see [llms.txt](https://ftcoders.first-tech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ftcoders.first-tech.com/first-tech-ttp-sdk/manual-checkout.md).
# Manual Checkout
**Objective**
Establish the **minimum requirements** for the manual checkout flow, enabling sellers to input transaction amounts, select a payment method, and complete the operation via NFC (Tap to Pay), with clarity, security, and efficiency.
#### Insights
* The flow must comply with **PCI MPoC** standards for proximity payments.
* NFC interaction must be tested across multiple device types (POS terminals and smartphones).
* The delay between payment method selection and NFC detection must not exceed 5 seconds, except in justified technical scenarios.
***
## Accessing the Checkout Flow
### 01 - “Charge” icon in bottom navigation
Must always be visible as a main navigation item. When selected, it must open the amount input screen.
{% hint style="success" %}
**Mandatory:**
The charge/checkout flow must be accessible from anywhere in the app and have visual emphasis equal to cart or catalog entries.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Show active focus feedback when the icon is tapped.
{% endhint %}
***
## Entering the Checkout Amount
### 02 - Amount input field
Must be centered, with readable font and active cursor. Only valid numeric input should be accepted.
### 03 - Quick amount suggestions
Predefined values (e.g., R$ 50, R$ 85) must be visible and tappable
### 04 - Custom numeric keypad
Must be in-app (not system default), with large, responsive buttons.
{% hint style="success" %}
**Mandatory:**
The “Continue” button must remain disabled until a value greater than zero is entered.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Automatically apply currency formatting while typing (e.g., 12200 → 122.00).
{% endhint %}
***
## Selecting Payment Method
### 05 - Payment method modal
Must include at least the following:
* Tap to Pay
* Pix
* Payment Link\
Order may vary, but Tap to Pay must be clearly visible and accessible.
{% hint style="success" %}
**Mandatory:**
Selection must be clear, with both icon and label, following accessibility standards.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Remember the last selected payment method for faster reuse.
{% endhint %}
***
## Tap to Pay Definition
### 06 - Credit/Debit selection
User must select between “Credit” or “Debit”, with clear visual indicatio
### 07 - Installment options (if applicable)
If “Credit” is selected, show available installments with per-installment value and total
### 08 - “Continue” button
Only enabled after selecting both payment type and number of installments (if required)
{% hint style="success" %}
**Mandatory:**
Payment options must comply with card network and terminal rules.
{% endhint %}
{% hint style="info" %}
**Recommended:**
Show a summary of the selected options before moving to the final checkout screen.
{% endhint %}
***
## Checkout via NFC
**NFC prompt screen**
Must show final amount and payment type (e.g., “Credit – one-time”) with clear illustration of card or phone proximity gesture.
{% hint style="success" %}
**Mandatory:**
The system must wait for NFC proximity and process payment automatically upon detection
{% endhint %}
{% hint style="info" %}
**Recommended:**
Provide visual feedback (e.g., animation, sound, vibration) upon successful detection and completion.
{% endhint %}
***
## Mandatory Messages
* When no amount is entered:
> Please enter an amount to continue.
* When NFC is not detected:
> No contact detected. Please adjust the positioning and try again.
## Expected Behaviors
* The full flow must be concise (maximum 5 steps before payment).
* All values and options must be clearly visible at every step.
* The user must be able to correct inputs before final confirmation.
---
# 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://ftcoders.first-tech.com/first-tech-ttp-sdk/manual-checkout.md?ask=&goal=
```
`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.