Direct payment variables in your messages

What they are for

Variables are snippets you write into a message that the system replaces with the real data at sending time. That way you write one message and it goes out personalised on every booking.

The variables below bring in the payment details registered on that booking's property.

The eight payment variables

{{beneficiaryName}} — the name of whoever will receive the payment.

{{pixKey}} — the registered Pix key.

{{pixKeyType}} — the key type (tax ID, company ID, email, phone or random key).

{{bankName}} — the bank.

{{bankAgency}} — the branch.

{{bankAccount}} — the account.

{{bankAccountType}} — the account type (current or savings).

{{paymentInstructions}} — the free text you wrote under "Additional instructions" on the property.

They appear in the editor's variable list only in the Direct payment to the owner section, under Automations → Post-booking.

The manager and the payee are not the same person

This is the most expensive confusion of all, and worth remembering:

{{ownerName}} is the person responsible for your business — the account manager. It has the same meaning this variable already has in check-in and team messages. Use it to sign the message.

{{beneficiaryName}} is whoever will receive the payment for that property — the holder of the Pix key.

In operations that manage other people's properties, those two are almost never the same person. Using {{ownerName}} to say where to transfer the money would put the wrong name beside the Pix key.

When they are filled in

The payment variables only carry values in the Direct payment to the owner situation.

In the other situations — Pix via Asaas, Card via Asaas, Pay later and Default message — they come out deliberately blank. It is a protection: a guest who has already paid online must not receive a Pix key in the same message and end up paying twice.

If you preview one of those situations using these variables, the screen warns you that they would come out empty.

A variable with no data becomes an empty line

If a field is not registered on the property, the corresponding variable is replaced by nothing — the word "undefined" does not appear, nor does the variable name in braces.

In practice, that means writing the message in a way that still makes sense if, say, the bank account is not filled in.

Example message

Hi {{guestFirstName}}, your booking at {{propertyName}} is confirmed!

Check-in: {{checkInDate}}

Check-out: {{checkOutDate}}

Amount: {{totalAmount}}

To complete it, send the Pix to:

Payee: {{beneficiaryName}}

Key ({{pixKeyType}}): {{pixKey}}

{{paymentInstructions}}

Any questions, just reply.

{{ownerName}}

Common mistakes

Using {{ownerName}} where {{beneficiaryName}} was meant.

Using the payment variables in the default message and being surprised by blank lines.

Writing "Bank: {{bankName}}" on a property that only has a Pix key registered — the line comes out half finished.

Frequently asked questions

Do I need to type the Pix key into the message?

No, and it is better not to. Using {{pixKey}}, each property sends its own key, and one correction in the settings applies to every message from then on.

Do these variables work in Pipeline templates?

No. On a manual Pipeline send they would come out blank, which is why they are not offered on that screen. See the difference between the two areas.