Share transfer receipt — branded image export
Context
After completing a transfer in the Exa App, users currently take a raw screenshot of the success screen to send proof to the recipient. Other consumer fintech apps (Mercado Pago, Belo, etc.) ship a native share button on the post-transfer screen that exports a clean, branded image through the OS share sheet.
Goal: replace the screenshot workaround with a first-class share action that doubles as free distribution — every shared receipt carries the Exa App branding.
Priority: nice-to-have. Not on the near-term roadmap. Design exploration only at this stage.
📐 Scope & Requirements
In scope:
- Post-transfer receipt image with strong branding of the Exa App.
- "Share" button that triggers the native OS share sheet with a generated image of the transaction.
- Branded visual treatment of the exported image — Exa logo + "Powered by the Exa App" tagline.
Out of scope:
- Sharing flows for screens other than the transfer success state.
Requirements:
- The exported image must be legible as a standalone artifact when shared via WhatsApp, iMessage, Telegram, etc. (no context outside the image).
- Branding must be visible but not crowd the transaction data the recipient is actually looking for.
- Visual reference: Mercado Pago and Belo post-transfer share flows.
🎨 Design Tasks
🔗 Assets & Links
- Reference: Mercado Pago / Belo post-transfer share flows
🔴 Blocking reason (if applicable):
Share transfer receipt — branded image export
Context
After completing a transfer in the Exa App, users currently take a raw screenshot of the success screen to send proof to the recipient. Other consumer fintech apps (Mercado Pago, Belo, etc.) ship a native share button on the post-transfer screen that exports a clean, branded image through the OS share sheet.
Goal: replace the screenshot workaround with a first-class share action that doubles as free distribution — every shared receipt carries the Exa App branding.
Priority: nice-to-have. Not on the near-term roadmap. Design exploration only at this stage.
📐 Scope & Requirements
In scope:
Out of scope:
Requirements:
🎨 Design Tasks
🔗 Assets & Links
🔴 Blocking reason (if applicable):