Connect Vindi Recorrência with Pagar.me
Unlock the superpowers of Vindi Recorrência + Pagar.me and automate your tasks without having to write a single line of code.
Vindi Recorrência and Pagar.me
your way
Check out the available triggers and actions in the automation of apps Vindi Recorrência + Pagar.me
Charge refunded
For each reversed billing on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Charge refunded
For each reversed billing on Vindi RecorrênciaTrigger
billing id
expiration date (formatted - DD/MM/YYYY)
email customer
customer name
status
total amount
total amount (text)
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
Payment method
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
id and invoice
plan name
payment method name
Customer CPF/CNPJ
customer status
External code
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Created subscription
For each subscription created on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created subscription
For each subscription created on Vindi RecorrênciaTrigger
subscription id
start date (formatted - DD/MM/YYYY)
start day (formatted - DD)
end date (formatted - DD/MM/YYYY)
date of next invoice (formatted - DD/MM/YYYY)
cancellation date (formatted - DD/MM/YYYY)
Maximum number of subscription periods
late since (formatted - DD/MM/YYYY)
plan id
plan name
Plan code upon subscription
products name
products description
email customer
customer name
total discount amount
status
total amount
installments
Payment method
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
billing date current period (YYYY-MM-DDTHH:mm:ss-Z)
start date of the current period (formatted - DD/MM/YYYY)
end date of the current period (formatted - DD/MM/YYYY)
customer id
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Approved payment
For each approved payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved payment
For each approved payment on Pagar.meTrigger
transaction id
tid of the acquirer
not as a buyer
status
código
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
ticket: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Acquirer fee (in cents) [only pagar.me 1.0]
Acquirer fee [only pagar.me 1.0]
Acquirer fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
List of IDs of sales intermediaries [only pagar.me 1.0]
List of amounts per sales intermediary [only pagar.me 1.0]
Pix: QR Code
Pix: Expiration Date
Pix: Name of the payer [only pagar.me 1.0]
Pix: Payer document [only pagar.me 1.0]
Pix: Payer document type [only pagar.me 1.0]
Pix: Name of the payer’s Bank [only pagar.me 1.0]
Pix: ISPB code of the payer's bank [only pagar.me 1.0]
Pix: Payer's bank branch [only pagar.me 1.0]
Pix: Payer's bank account number [only pagar.me 1.0]
Declined payment
For each declined payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Declined payment
For each declined payment on Pagar.meTrigger
transaction id [only pagar.me 1.0]
tid of the acquirer
not as a buyer
status
código
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
bank slip: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Purchaser fee (in cents) [only pagar.me 1.0]
Purchaser fee [only pagar.me 1.0]
Purchaser fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
Charge declined
For each declined billing on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Charge declined
For each declined billing on Vindi RecorrênciaTrigger
billing id
expiration date (formatted - DD/MM/YYYY)
email customer
customer name
status
total amount
total amount (text)
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
Payment method
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
id and invoice
plan name
payment method name
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Approved invoice
For each approved invoice on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Approved invoice
For each approved invoice on Vindi RecorrênciaTrigger
invoice id
expiration date (formatted - DD/MM/YYYY)
expiration date - charges (formatted - DD/MM/YYYY)
invoice url
email customer
customer name
status
total amount
total amount (text)
total amount paid of charges
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created on (day - DD)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
Payment method
Payment company code
items name
items description
Total discount amount of items (Positive)
Amount of items separated by comma
Formatted amount of items separated by comma
creation date of the item pricing scheme
charges information
charges: gateway authorization
charges: gateway response fields
cobranças: NSUs (separados por vírgula)
subscription id
plan id on subscription
plan name on subscription
Plan code upon subscription
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Fiscal Note: Id
Invoice: External integration code
Invoice: Number or reference at the government institution
Tax Note: Amount
Nota Fiscal: Status
Invoice: URL
Invoice: Description
Invoice: Date and time of issue
Invoice: Competence date
Invoice: Date and time of appointment
Invoice: Date and time of generation
Invoice: Date and time of last update
Period Cycle
Fim do período contratado
Metadata summary
Metadata amounts
Created payment
For each created payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created payment
For each created payment on Pagar.meTrigger
transaction id
tid of the acquirer
not as a buyer
status
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
bank slip: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Purchaser fee (in cents) [only pagar.me 1.0]
Purchaser fee [only pagar.me 1.0]
Purchaser fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
Pix: QR Code
Pix: Expiration Date
Pix: Name of the payer [only pagar.me 1.0]
Pix: Payer document [only pagar.me 1.0]
Pix: Payer document type [only pagar.me 1.0]
Pix: Name of the payer’s Bank [only pagar.me 1.0]
Pix: ISPB code of the payer's bank [only pagar.me 1.0]
Pix: Payer's bank branch [only pagar.me 1.0]
Pix: Payer's bank account number [only pagar.me 1.0]
Canceled subscription
For each subscription canceled on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Canceled subscription
For each subscription canceled on Vindi RecorrênciaTrigger
subscription id
start date (formatted - DD/MM/YYYY)
end date (formatted - DD/MM/YYYY)
date of next invoice (formatted - DD/MM/YYYY)
cancellation date (formatted - DD/MM/YYYY)
Maximum number of subscription periods
late since (formatted - DD/MM/YYYY)
plan id
plan name
Plan code upon subscription
products name
products description
email customer
customer name
status
total amount
installments
Payment method
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
billing date current period (YYYY-MM-DDTHH:mm:ss-Z)
start date of the current period (formatted - DD/MM/YYYY)
end date of the current period (formatted - DD/MM/YYYY)
customer id
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Created invoice
For each created invoice on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Created invoice
For each created invoice on Vindi RecorrênciaTrigger
id and invoice
expiration date (formatted - DD/MM/YYYY)
expiration date - charges (formatted - DD/MM/YYYY)
invoice url
email customer
customer name
status
total amount
total amount (text)
installments
created in (YYYY-MM-DDTHH:mm:ss-Z)
created on (DD/MM/YYYY)
created on (day - DD)
created in (H:M:S)
created in (DD/MM/YYYY - H:M:S)
updated in (YYYY-MM-DDTHH:mm:ss-Z)
updated on (DD/MM/YYYY)
updated in (H:M:S)
updated in (DD/MM/YYYY - H:M:S)
paid in (YYYY-MM-DDTHH:mm:ss-Z)
paid in (DD/MM/YYYY)
paid in (H:M:S)
paid in (DD/MM/YYYY - H:M:S)
customer id
Payment method
items name
items description
Valor total do desconto dos itens (Positivo)
Valor dos items separado por vírgula
Valor formatado dos items separado por vírgula
data de criação do esquema de precificação dos items
charges information
charges: gateway authorization
charges: gateway response fields
subscription id
plan id on subscription
plan name on subscription
Plan code upon subscription
Customer CPF/CNPJ
External code
customer status
mobile customer
landline customer
customer address Zip Code
customer street address
customer address number
customer address neighborhood
customer address city
customer address state
customer country address
customer add-on address
Refunded payment
For each refunded payment on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Refunded payment
For each refunded payment on Pagar.meTrigger
transaction id
tid of the acquirer
not as a buyer
status
status reason [only pagar.me 1.0]
flag code
buyer's response
Message from the acquirer
creation date
creation date (formatted - DD/MM/YYYY)
creation date (formatted - H:M:S)
creation date (formatted - DD/MM/YYYY - H:M:S)
update date
update date (formatted - DD/MM/YYYY)
update date (formatted - H:M:S)
update date (formatted - DD/MM/YYYY - H:M:S)
total amount (in cents)
total amount
total amount (formatted in R$)
amount captured (in cents)
captured amount
amount captured (formatted in R$)
Total amount of items (in cents)
cost (in cents) [only pagar.me 1.0]
cost [only pagar.me 1.0]
cost (formatted in R$) [only pagar.me 1.0]
refunded amount (in cents) [only pagar.me 1.0]
amount refunded [only pagar.me 1.0]
refunded amount (formatted in R$) [only pagar.me 1.0]
payment method
installments
bank slip: link
bank slip: barcode
bank slip: expiration date
Subscription ID [only pagar.me 1.0]
customer telephone number (ddi)
customer phone number (ddd)
customer telephone number (number)
customer: document
customer: email
customer: name
address street
address: number
full address
address neighborhood
address: city
address: state
address: Zip Code
billing address: street
billing address: number
billing address: add-on
billing address: neighborhood
billing address: city
billing address: state
billing address: Zip Code
delivery address: street [only pagar.me 1.0]
delivery address: number [only pagar.me 1.0]
delivery address: complement [only pagar.me 1.0]
delivery address: neighborhood [only pagar.me 1.0]
delivery address: city [only pagar.me 1.0]
delivery address: state [only pagar.me 1.0]
delivery address: Zip Code [only pagar.me 1.0]
Shipping fee (in cents) [only pagar.me 1.0]
Shipping fee [only pagar.me 1.0]
Item SKU/ID
item title
unit price of items
quantity of items
title, price and quantity of items
Purchaser fee (in cents) [only pagar.me 1.0]
Purchaser fee [only pagar.me 1.0]
Purchaser fee (formatted in R$) [only pagar.me 1.0]
Advance fee (in cents) [only pagar.me 1.0]
Advance fee [only pagar.me 1.0]
Advance fee (formatted in R$) [only pagar.me 1.0]
payment link: id [only pagar.me 1.0]
payment link: name [only pagar.me 1.0]
card flag
Pix: QR Code
Pix: Expiration Date
Pix: Name of the payer [only pagar.me 1.0]
Pix: Payer document [only pagar.me 1.0]
Pix: Payer document type [only pagar.me 1.0]
Pix: Name of the payer’s Bank [only pagar.me 1.0]
Pix: ISPB code of the payer's bank [only pagar.me 1.0]
Pix: Payer's bank branch [only pagar.me 1.0]
Pix: Payer's bank account number [only pagar.me 1.0]
Create customer
create a customer on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create customer
create a customer on Vindi RecorrênciaAction
name Required
telephone
cell phone
document
External code
Zip Code address
address street
address number
full address
address neighborhood
city address
state address
country address
Generate billing
generate a billing on Pagar.meHow it works:
Whenever something happens on the source app
All happening in a single automation! ✨
Generate billing
generate a billing on Pagar.meAction
Payment method Required
Payment deadline Required
Amount Required
Customer email Required
Customer name
Customer Type Required
CPF/CNPJ (Individual Person Registry/National Legal Entity Registry) Required
Description
Notify customer of billing
Create subscription
create a subscription on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create subscription
create a subscription on Vindi RecorrênciaAction
customer name Required
email customer
Subscription start date
Payment method Required
Plan selection form
Plan
Plan
Plan
Plan interval count
Plan billing cycles
plan billing trigger type
billing trigger day
plan code
plan description
plan item name
plan item price
plan item code
plan item description
plan item unit of measurement
telephone
cell phone
document
Update customer based on
Customer Code
Zip Code address
address street
address number
full address
address neighborhood
city address
state address
country address
Create invoice
Create invoice on Vindi RecorrênciaHow it works:
Whenever something happens on the source app
1.
All happening in a single automation! ✨
Create invoice
Create invoice on Vindi RecorrênciaAction
Update customers
Customer: Name Required
Customer: Email
Customer: CPF/CNPJ
Invoice: Payment method Required
Invoice: Due date
Item: Name Required
Item price Required
Item: Quantity
Item: Code
Customer: Telephone
Customer: Cellphone
Customer: Code
Customer: Zip code
Customer: Street
Customer: Address number
Customer: Address complement
Customer: Neighborhood
Customer: City
Customer: State
Customer: Country
Didn't find your use case? Send suggestion.
Automate Vindi Recorrência and Pagar.me with Pluga integrations
Explore automation templates
For each approved payment on Pagar.me, create a customer on Vindi Recorrência
EXPLORE For each created payment on Pagar.me, create a customer on Vindi Recorrência
EXPLORE For each approved payment on Pagar.me, create invoice on Vindi Recorrência
EXPLORE Miss an automation with this apps?
Say to us!Trusted by over 10.000 amazing companies
How to integrate apps with Pluga?
Pluga allows you to integrate two or more apps in a simple, practical way without needing to type a single line of code. Here are the steps to automate your tasks and start focusing on what really matters.
-
What is the automation trigger?
The trigger is the step that initiates automation. In the integration process, it is selected after choosing the source app. For example, if you choose Facebook Lead Ads as the source app, the trigger could be: For each response on an advertisement.
-
What is an action within an automation?
The action serves as a response to the previously selected trigger. That is, it occurs once the trigger is activated. For example, in an automation between Facebook Lead Ads (source) and Google Sheets (destination), as soon as the trigger “For each response on an advertisement” is activated in the source app, the action “Add data to a new row on a spreadsheet” will be carried out in the destination app.
-
How does information mapping work?
Information mapping is where you configure which captured information from the source app will be sent to each field in the destination app(s).
For example, in an automation between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.
-
Is it possible to have more than one action?
With Pluga, you can create automations by integrating several apps at once. For example, you can integrate Facebook Lead Ads + Google Sheets + Slack, so when the trigger is activated, the first action is executed and a notification is sent via Slack.
Automate Vindi Recorrência + Pagar.me
and say goodbye to manual (and tedious) tasks!
By connecting the apps you use through Pluga, you can automate various processes in your routine and have time for tasks that really matter. 
Vindi Recorrência
PaymentVindi Recorrência is a payment management platform that helps businesses automate billing, manage subscriptions, default control, and improve financial management.
Integrations with Vindi Recorrência Visit Vindi Recorrência Pagar.me
PaymentPagar.me is an online payment platform offering solutions for businesses to receive payments via credit card, payslip, bank transfer, and other payment methods.
Integrations with Pagar.me Visit Pagar.me