Connect Pagar.me with Moskit CRM

Unlock the superpowers of Pagar.me + Moskit CRM and automate your tasks without having to write a single line of code.

Pagar.me and Moskit CRM
your way

Check out the available triggers and actions in the integration of apps Pagar.me + Moskit CRM and build your automation

Pagar.me-icon

Approved payment

For each approved payment on Pagar.me

Trigger

Information from Pagar.me that can be used and sent to other apps.

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]

Pagar.me-icon

Declined payment

For each declined payment on Pagar.me

Trigger

Information from Pagar.me that can be used and sent to other apps.

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

Moskit CRM-icon

Created deal

For each created deal on Moskit CRM

Trigger

Information from Moskit CRM that can be used and sent to other apps.

Deal: ID

Deal: Name

Deal: Expected Date

Deal: Amount in cents

Deal: Status

Deal: Number of projects running

Deal: Number of archived projects

Deal: Created by

Deal: Responsible

Deal: Stage

Deal: Pipeline

Deal: Pipeline ID

Deal: Amount

Deal: Creation date

Deal: Date of last stage change

Deal: Closing date

Deal: Product SKU separated by comma

Deal: Name of products separated by comma

Deal: SKU and Product name separated by comma

Deal: Name, quantity and price of products separated by commas

Contact: Name

Contact: Main Telephone

Contact: Principal Email

Contact: Telephone numbers separated by commas

Contact: Comma-separated emails

Contact: Website

Contact: Creation Date

Contact: Created by

Contact: Responsible

Contact: Observations

Company: Name

Company: Main Telephone

Company: Main Email

Company: Comma separated telephone numbers

Company: Comma separated emails

Company: Website

Company: Creation Date

Company: Created by

Company: Responsible

Moskit CRM-icon

Won deal

For each won deal on Moskit CRM

Trigger

Information from Moskit CRM that can be used and sent to other apps.

Deal: ID

Deal: Name

Deal: Expected Date

Deal: Amount in cents

Deal: Status

Deal: Number of projects running

Deal: Number of archived projects

Deal: Created by

Deal: Responsible

Deal: Stage

Deal: Pipeline

Deal: Pipeline ID

Deal: Amount

Deal: Creation date

Deal: Date of last stage change

Deal: Closing date

Deal: Product SKU separated by comma

Deal: Name of products separated by comma

Deal: SKU and Product name separated by comma

Deal: Name, quantity and price of products separated by commas

Contact: Name

Contact: Main Telephone

Contact: Principal Email

Contact: Telephone numbers separated by commas

Contact: Comma-separated emails

Contact: Website

Contact: Creation Date

Contact: Created by

Contact: Responsible

Contact: Observations

Company: Name

Company: Main Telephone

Company: Main Email

Company: Comma separated telephone numbers

Company: Comma separated emails

Company: Website

Company: Creation Date

Company: Created by

Company: Responsible

Pagar.me-icon

Created payment

For each created payment on Pagar.me

Trigger

Information from Pagar.me that can be used and sent to other apps.

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]

Pagar.me-icon

Created subscription

For each created subscription on Pagar.me

Trigger

Information from Pagar.me that can be used and sent to other apps.

Transaction: ID

Subscription: Creation date

Subscription: Creation date (format - DD/MM/YYYY)

Subscription: Creation hour (format - H:M:S)

Subscription: Creation date (format - DD/MM/YYYY - H:M:S)

Subscription: Update date

Subscription: Update date (format - DD/MM/YYYY)

Subscription: Update date (format - H:M:S)

Subscription: Update date (format - DD/MM/YYYY - H:M:S)

Subscribed: Total price (in cents)

Subscribed: Total price

Subscribed: Total price (format - R$)

Client: Telephone (DDI)

Client: Telephone (DDD)

Client: Telephone

Client: Document

Client: Email

Client: Name

Address: Street

Address: Number

Address: Complement

Address: Neighborhood

Address: City

Address: State

Address: CEP

Subscribed: Current period start

Subscribed: Current period start (format - DD/MM/YYYY)

Subscribed: Current period start (format - H:M:S)

Subscribed: Current period start (format - DD/MM/YYYY - H:M:S)

Subscribed: Current period end

Subscribed: Current period end (format - DD/MM/YYYY)

Subscribed: Current period end (format - H:M:S)

Subscribed: Current period end (format - DD/MM/YYYY - H:M:S)

Transaction: Payment method

Transaction: Card holder name

Transaction: Card brand

Subscribed: Metadata origin

Subscribed: Metadata internal name

Subscribed: Items description resume, separated by comma [only pagar.me 2.0]

Subscribed: Quantity items resume, separated by comma [only pagar.me 2.0]

Subscribed: Items price resume, separated by comma [only pagar.Me 2.0]

Subscribed: Description, price and quantity resume, separated by comma [only pagar.me 2.0]

Subscribed: Next billing dates [only pagar.me 2.0]

Subscribed: Next billing dates (format - DD/MM/YYYY) [only pagar.me 2.0]

Subscribed: Next billing dates (format - H:M:S) [only pagar.me 2.0]

Subscribed: Next billing dates (format - DD/MM/YYYY - H:M:S) [only pagar.Me 2.0]

Moskit CRM-icon

Lost deal

For each lost deal on Moskit CRM

Trigger

Information from Moskit CRM that can be used and sent to other apps.

Deal: ID

Deal: Name

Deal: Expected Date

Deal: Amount in cents

Deal: Status

Deal: Number of projects running

Deal: Number of archived projects

Deal: Created by

Deal: Responsible

Deal: Stage

Deal: Pipeline

Deal: Pipeline ID

Deal: Amount

Deal: Creation date

Deal: Date of last stage change

Deal: Closing date

Deal: Product SKU separated by comma

Deal: Name of products separated by comma

Deal: SKU and Product name separated by comma

Deal: Name, quantity and price of products separated by commas

Contact: Name

Contact: Main Telephone

Contact: Principal Email

Contact: Telephone numbers separated by commas

Contact: Comma-separated emails

Contact: Website

Contact: Creation Date

Contact: Created by

Contact: Responsible

Contact: Observations

Company: Name

Company: Main Telephone

Company: Main Email

Company: Comma separated telephone numbers

Company: Comma separated emails

Company: Website

Company: Creation Date

Company: Created by

Company: Responsible

Deal: Reason for loss

Pagar.me-icon

Refunded payment

For each refunded payment on Pagar.me

Trigger

Information from Pagar.me that can be used and sent to other apps.

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]

Moskit CRM-icon

Created contact

For each created contact on Moskit CRM

Trigger

Information from Moskit CRM that can be used and sent to other apps.

Name

Main Phone

E-mail Principal

Telephone numbers separated by comma

Emails separated by comma

Site

Creation date

Created by

Responsible

Comments

Company: Name

Company: Main Telephone

Company: Main Email

Company: Comma separated telephone numbers

Company: Comma separated emails

Company: Website

Company: Creation Date

Company: Created by

Company: Responsible

Moskit CRM-icon

Deal reached stage

When a deal reaches a funnel stage on Moskit CRM

Trigger

Information from Moskit CRM that can be used and sent to other apps.

Deal: ID

Deal: Name

Deal: Expected Date

Deal: Amount in cents

Deal: Status

Deal: Number of projects running

Deal: Number of archived projects

Deal: Created by

Deal: Responsible

Deal: Stage

Deal: Pipeline

Deal: Pipeline ID

Deal: Amount

Deal: Creation date

Deal: Date of last stage change

Deal: Closing date

Deal: Product SKU separated by comma

Deal: Name of products separated by comma

Deal: SKU and Product name separated by comma

Deal: Name, quantity and price of products separated by commas

Contact: Name

Contact: Main Telephone

Contact: Principal Email

Contact: Telephone numbers separated by commas

Contact: Comma-separated emails

Contact: Website

Contact: Creation Date

Contact: Created by

Contact: Responsible

Contact: Observations

Company: Name

Company: Main Telephone

Company: Main Email

Company: Comma separated telephone numbers

Company: Comma separated emails

Company: Website

Company: Creation Date

Company: Created by

Company: Responsible

Pagar.me-icon

Create customer

create a customer on Pagar.me

Action

Fields in Pagar.me that can receive information from other apps.

Customer: Name Required

Customer: Email Required

Customer: CPF/CNPJ

Address: Street Required

Address: Number Required

Address: Additional information

Address: City

Address: State

Address: Country

Address: Zip Code Required

Customer: Area code of the phone Required

Customer: Telephone Required

Customer: International dialing code

Moskit CRM-icon

Create or update deal

create or update a business on Moskit CRM

Action

Fields in Moskit CRM that can receive information from other apps.

Distribute new deal Required

Select sellers

Responsible

Deal Name Required

Company: Name

Contact: Name

Contact: Email

Amount

Expected date

Deal status

Closing date

Reason for loss

Update Main Company

Company: Email

Company: Telephone

Update Primary Contact

Contact: Telephone

Contact: Position

Product's name

Product SKU

Product quantity

Price of the product

Company: Website

Company: Observations

Contact: Observations

Contact updates

Pagar.me-icon

Generate billing

generate a billing on Pagar.me

Action

Fields in Pagar.me that can receive information from other apps.

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

Moskit CRM-icon

Create or update contact

create or update a contact on Moskit CRM

Action

Fields in Moskit CRM that can receive information from other apps.

Select responsible Required

Contact: Name

Contact: Email Required

Contact: CPF

Company: Name

Company: Email

Company: CNPJ

Contact: Position

Contact: Telephone

Contact: Observations

Company: Website

Company: Telephone

Company: Observations

Contact updates

Didn't find your use case? Send suggestion.

Automate Pagar.me and Moskit CRM
with Pluga integrations

Explore automation templates

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.

  • Trigger and source app of the integration

    What is the integration 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.

  • Action and destination app of the integration

    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 integration 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.

  • Information mapping of the integration

    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 integration between Facebook Lead Ads and Google Sheets, this step is where you will determine which contact information should fill in the spreadsheet fields.

  • Integrations with multiple actions among more than two apps

    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.

Integrate Pagar.me + Moskit CRM
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.

Automatic transfer of your contacts' information to other apps

Automating the transfer of your contact base (leads) information to other apps can greatly facilitate tasks that involve managing them.

At Pluga, you can do this with ease and also helps optimize the work of people, avoiding possible human errors.

Card with contact information being sent to other apps

Automate your sales tracking

With the help of Pluga's integrations, you can put your business's sales control on autopilot. This way, tasks surrounding inventory, finance, and logistics can be more aligned and optimized, directly impacting your customer's satisfaction.

Data from a new sale being sent to a spreadsheet

Automated financial control

Dealing with finances requires a lot of attention. For this, integrating apps can be a great ally! With Pluga, you can connect your financial management software and payment methods to other apps to automate tasks involving the organization of your finances.

Data from a new charge being sent to an invoicing app

Reduce communication noise - and rework!

If your company uses any type of internal communication tool, it's possible to automate the routine of notifications and alerts within it.

At Pluga, for example, you can connect this software to your project management platform so that every time a task changes status, this is communicated in a channel. In other words, it increases productivity, reduces communication noise, and avoids possible rework.

Automatic notification in the internal communication app

Customized alerts for customers

Often, personalized communication is what will captivate a customer to keep them interested in your brand. But doing this manually is almost impossible. Using Pluga, you can send these notifications automatically without losing personalization.

Automatic message sent to the customer's WhatsApp
Pagar.me-icon

Pagar.me

Payment

Pagar.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
Moskit CRM-icon

Moskit CRM

CRM

Moskit CRM is a customer relationship management (CRM) platform that offers tools to organize contacts, track sales, automate tasks, and improve customer relationships.

Integrations with Moskit CRM Visit Moskit CRM

Frequently Asked Questions

  • With Pluga, you can easily integrate Pagar.me com Moskit CRM . Just follow these steps:

    • 1. Log in or sign up (for free) on Pluga and click on “Create automation”;
    • 2. Select the source app and trigger;
    • 3. Select the destination app and action;
    • 4. Make the necessary adjustments, specifying which data will be sent to one app to another.
  • By integrating Pagar.me with Moskit CRM on Pluga, you can automate various manual tasks that reduce productivity for those who perform them, while also avoiding human errors. The best part is that the process is simple and doesn’t require typing a single line of code.

  • On Pluga, you can make several integrations for free with the free plan. Additionally, you have the option to try all the features for 7 days at no cost to create integrations between Pagar.me, Moskit CRM, and even other apps.

    We also offer three other plans, with prices ranging from $17 to $65 per month, which include premium automations and features, as well as a higher volume of events and automations. For companies with specific needs, we have the Enterprise plan, designed to offer customized solutions beyond the resources available in other plans.

    Check Pluga's pricing page for more details.