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.


Access to Receipt Delivery

01 - “Send receipt” button

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

Recommended:

Include a share icon next to the button label for visual clarity.


Delivery Method Modal

02 Delivery options

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

  • QR Code

  • Email

  • Phone number (SMS/WhatsApp) |

Recommended:

Prioritize the most frequently used channels based on user history.


Phone Delivery Flow

03 - “Phone number” field

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

04 - “Send” button

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

Recommended:

Allow the user to save the number for future transactions (with consent).


Receipt View

05 - “Order” section

Must include:

  • Store name

  • Tax ID (CNPJ)

  • Date and time

  • Order number

  • Payment method

06 - “Products” section

Itemized list including product names, individual prices, subtotal, discount, and total amount.

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.

Recommended:

Allow download as PDF or enable offline access.


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.

Last updated