Skip to content
Explore the preview
Browse workflow ideas

Make payment requests clear before a customer scans to pay.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

Prepare a PIX QR code from the intended recipient’s valid Brazilian payment key, name, city, amount, and optional description. Show the important payment details alongside the scannable image so a person can catch mistakes before a customer sees it. Verify the recipient and amount, protect payment information, and require approval of the exact request and destination before sharing it. Preparing a QR code does not confirm that a payment has been made.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
A PIX payment request needs preparationVerified recipient details and an agreed payment amount
“Prepare a clear PIX payment QR code and check the recipient, amount, and description before it is shared.”
Work through the request.

Clear tasks, with review where it matters.

  1. Confirm the recipient and payment purpose
  2. Check the amount and description
  3. Prepare the payment QR image
See all 5 tasks
A scannable payment request with readable details, approved for the intended customer and purpose.

What this workflow could do

Helps a business prepare Brazilian PIX payment requests with the details visible for review before a customer chooses to pay.

Review points proposed in this idea

An incorrect payment key, recipient name, amount, or description can direct money to the wrong place. Verify every detail with the recipient, keep payment information restricted, and require an authorized person to approve the exact QR image and its destination before external sharing. A generated request is not evidence of payment or settlement.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Verify the recipient’s payment key, displayed name, and city against a trusted business record.

Step 1 of 5

Confirm the recipient and payment purpose

Verify the recipient’s payment key, displayed name, and city against a trusted business record.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Define eligible payment details

    Specify accepted PIX key types, required recipient information, currency, and permitted payment purposes.

  2. 02

    Set amount and description controls

    Choose limits, required confirmations, and how missing or unusual payment details are handled.

  3. 03

    Protect recipient and transaction information

    Limit access to payment details and avoid including personal information that is unnecessary for the request.

  4. 04

    Assign payment reviewers

    Name who verifies recipient details and who approves each final request and its customer-facing destination.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation