Integrations · AbacatePay
AbacatePay revenue, in the same picture as the rest.
If you charge through AbacatePay, by card or Pix, that revenue does not exist in Stripe. Keep reads it with a read-only key and puts it next to your other billing sources — in the MRR, in the list of accounts, and in the risk.
What changes with AbacatePay connected
AbacatePay subscriptions join the overview and the accounts list, beside anything from Stripe or Asaas. Each currency totals within itself; Keep never converts reais into dollars.
With a usage source, AbacatePay customers get the same risk reasons as everyone else — usage dropped, went silent, no activity in 30 days — ordered by the MRR each one represents.
AbacatePay does not say how often a subscription charges, so Keep infers each billing cycle from your product catalog. Whatever cannot be inferred stays out of MRR rather than becoming a guess.
What Keep reads, writes, and stores
| — | Keep and AbacatePay |
|---|---|
| Connection | An API key you create with read-only permission and paste in Keep. Test (dev mode) keys work too. |
| Reads | Subscriptions (amount, status, trial), customers (name and email), and products, to infer billing cycles. |
| Writes | Nothing. A read-only key cannot, and Keep does not ask for more. |
| Stores | The key, encrypted with AES-256-GCM, and the last characters so you can tell which key is connected; the webhook secret; subscription changes received by webhook. |
| Webhook | Optional. Keep generates an address and a secret for your connection; you register them in AbacatePay (Webhook v2) for subscription.completed and subscription.cancelled. Deliveries are authenticated by that per-connection secret, compared in constant time. |
How to connect
Create a read-only key
In the AbacatePay dashboard, create an API key with read permission.
Paste it in Keep
Keep reads with it before saving. A key that does not answer is refused, not stored.
Turn on the webhook (optional)
Generate the address in Keep and register it in AbacatePay, so cancellations show up as they happen instead of at the next read.
Questions
- Why does Keep ask for a read-only key?
- Because reading is all it does. A key that could write is access Keep does not need to hold.
- Why do I have to register the webhook myself?
- A read-only key cannot create webhooks in AbacatePay. Keep gives you the address and the secret to paste; without the webhook, changes arrive at the next read.
- Can I use AbacatePay and Stripe together?
- Yes. Monitored MRR adds every billing source you connect, and each currency is shown on its own.
- Which plan includes AbacatePay?
- Every plan. All Keep features, including every integration, are in all plans; the difference between plans is monitored MRR.
Other integrations
Bring your AbacatePay revenue into view.
Paste a read-only key and see your subscriptions, MRR, and at-risk accounts in minutes.