> 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/payment-receipt-delivery.md).

# Payment Receipt Delivery

**Objective**

Establish the **minimum requirements** for sending payment receipts to customers after a transaction is completed. This step must allow fast, secure, and clear sharing through different channels, ensuring both traceability and ease of use.

#### Insights

* It's recommended that the receipt include a unique transaction identifier (hash or order ID) for internal tracking.
* Delivery channels must follow best security practices (e.g., verified sender domains for email).
* This flow must support auditing for tax compliance and customer service validation.

***

<figure><img src="https://732834971-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRHBTYHK49B1fSJrGzk2y%2Fuploads%2F7NNGADvFMeKQaP8oPaR3%2FSe%C3%A7%C3%A3o%204%20Envio%20de%20comprovante.png?alt=media&amp;token=24bd28e1-c6a7-4c4a-84a8-00ced778a398" alt=""><figcaption></figcaption></figure>

## Access to Receipt Delivery

### 01 - “Send receipt” button&#x20;

Must be available immediately after transaction approval, before completing the purchase. It should open the delivery method selection modal

{% hint style="success" %}
**Mandatory:**&#x20;

Sending the receipt must not block the ability to complete the purchase.
{% endhint %}

{% hint style="info" %}
**Recommended:**&#x20;

Include a share icon next to the button label for visual clarity.
{% endhint %}

***

## Delivery Method Modal

### 02 Delivery options&#x20;

Must be listed with icons and labels, including at least:

* QR Code
* Email
* Phone number (SMS/WhatsApp) |

{% hint style="success" %}
**Mandatory:**&#x20;

Modal must be easy to navigate and automatically close after a successful send.
{% endhint %}

{% hint style="info" %}
**Recommended:**&#x20;

Prioritize the most frequently used channels based on user history.
{% endhint %}

***

## Phone Delivery Flow

### 03 - “Phone number” field&#x20;

Must allow formatted input (e.g., (11) 91234-5678) and validate the number pattern.

### 04 - “Send” button&#x20;

Must remain disabled until a valid number is entered. After submission, display confirmation (e.g., “Receipt sent successfully”).

{% hint style="success" %}
**Mandatory:**&#x20;

Delivery via phone must be processed through a verified messaging service (with auditable trace).
{% endhint %}

{% hint style="info" %}
**Recommended:**&#x20;

Allow the user to save the number for future transactions (with consent).
{% endhint %}

***

## Receipt View

### 05 - “Order” section&#x20;

Must include:

* Store name
* Tax ID (CNPJ)
* Date and time
* Order number
* Payment method

### 06 - “Products” section&#x20;

Itemized list including product names, individual prices, subtotal, discount, and total amount.&#x20;

### 07 - “Customer support” section

Contact information for post-sale support, including email and WhatsApp.

### 08 - “Start” button

Must return to the home screen with the session cleared.

{% hint style="success" %}
**Mandatory:**&#x20;

The receipt must be generated locally and optionally available via link or downloadable file.
{% endhint %}

{% hint style="info" %}
**Recommended:**&#x20;

Allow download as PDF or enable offline access.
{% endhint %}

***

## Mandatory Messages

* If the number is invalid:

  > Please enter a valid phone number to send the receipt.
* After successful delivery:

  > Receipt sent successfully!
* If delivery fails:

  > Failed to send receipt. Please check your connection or try again.

## Expected Behaviors

* Receipt delivery must be non-blocking (UI should remain responsive).
* The receipt must accurately reflect the details of the completed transaction.
* All sensitive data must be encrypted and compliant with privacy policies.
* The receipt screen must remain fully legible on small devices.


---

# 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://ftcoders.first-tech.com/first-tech-ttp-sdk/payment-receipt-delivery.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.