Connect a Payment Portal with Asaas

Summary Accept online payments on your captive portal — Pix, credit card, and boleto — using your own Asaas account. Guests pay you directly; MKController orchestrates the checkout and releases internet access once Asaas confirms the payment. Asaas uses a single credential: one API key ($aact_prod_…) from your Asaas settings.

Asaas uses a single credential — one API key:

Field in MKController	What it is	Format
API key	Your account’s production API key	$aact_prod_…

The key starts with the literal $ ($aact_prod_…). Copy it exactly, including the $.

1. Sign in at asaas.com.
2. Open Settings → Integrations → API Key (Configurações → Integrações → Chave de API).
3. Click Generate API Key (or copy the existing one) and copy the whole value — it starts with $aact_prod_.

Keep in mind:

• Account approval. Production API keys only authenticate after Asaas approves your account (documents/registration). If the key is rejected, check that your account status is approved.
• IP restriction. If you enabled an IP allow‑list on the API key in Asaas, it must permit MKController’s servers — otherwise the key is rejected.
• Pix. To receive by Pix, register at least one Pix key on the Asaas account.

1. Open Integrations → Payments.
2. Select the Payment gateways tab.
3. Find Asaas and click Configure.
4. Paste your API key ($aact_prod_…).
5. Click Validate and connect.

MKController validates the key against Asaas and loads the supported methods (Pix, credit card, boleto), shown as chips on the Asaas card. It also registers a webhook on your Asaas account automatically (so it is notified when a payment settles) and turns off Asaas’s own SMS/e‑mail/WhatsApp reminders for these charges, so your guests are not messaged directly.

1. Under Integrations → Payments, open the Payment methods tab.
2. Turn on the methods to accept — Pix, Credit card (and Boleto if you use it).
3. If a method can be processed by more than one connected gateway, use the Processed by dropdown to select Asaas.

1. Open the voucher → Integrations tab.
2. Under Online payment, switch on the methods this voucher should offer (e.g. Pix, Credit card).
3. Save.

On the captive portal for that voucher:

• Pix shows a copy‑and‑paste code the guest pays in their bank app.
• Card hands the guest off to Asaas’s secure invoice page, then returns them to the portal.

Once Asaas confirms the payment, the guest’s access is upgraded to the plan they bought.

• Make a real, low‑value purchase from a device on the hotspot to confirm the full flow.
• Track payments in the voucher’s Real time screen — gateway and paid/pending status show per session.
• Review every transaction in your Asaas → Charges / Transactions.

MKController field	Where to get it in Asaas
API key ($aact_prod_…)	Settings → Integrations → API Key → Generate / Copy

• “Invalid API key.” Re‑copy the key including the leading $, confirm your Asaas account is approved for production, and check whether an IP restriction on the key is blocking MKController’s servers.
• Charge fails to create. Asaas requires the payer’s CPF/CNPJ on every charge. Enable a CPF field on the captive form (in the Captive Portal Builder) so guests provide it before paying.
• Pix code isn’t generated. Confirm the account has an active Pix key registered in Asaas.
• Rotate a key? Generate a new API key in Asaas (this invalidates the old one), then click Reconnect on the Asaas card and paste the new value.

---

Explore next: Configure Payment Gateways · Receive Pix Payments · How Guests Connect & Pay

Need a hand? Talk to our team on WhatsApp or start your free MKController account.