FlowRunner
PricingContact
Theme
Start Free

Rebill

Payments

Rebill is a Latin American payments and subscriptions platform. Agents create customers, cards, and hosted payment links, run card and alternative-method checkouts, manage plans, coupons, and subscriptions, refund payments, and act on webhook events.

1 trigger 77 actions API key available
Rebill website Platform Documentation Capability data verified 2026-08-25
A subscription moves into defaulted after a scheduled charge fails
Get Subscription reads the status detail, which separates a customer pause from a payment failure
List Cards confirms whether a usable card is still on file for that customer
Create Card Update Link produces a short-lived hosted URL, delivered through your own channel
Agent waits for the card-updated event rather than assuming the customer acted on the link
Accounts still defaulted after the window are summarized with the amount at risk and the cycles missed
The revenue owner decides which accounts get charged now and which get a conversation first

What This Integration Enables

Rebill is built for selling on subscription across Latin America, and the design shows where the friction actually is in that market. Local alternative payment methods are first-class rather than an afterthought, and national identity documents sit on the customer record because several of those methods will not process without one. A device fingerprint feeds the acquirer's fraud engine, and a foreign exchange surface is bundled in because pricing in a volatile currency is part of the job rather than a separate problem.

The other thing Rebill gets right for agents is that it ships two ways to fix a dead card without charging anybody: it can contact the customer itself, or it can hand you a hosted link to deliver however you like. FlowRunner agents run all of that continuously, and they use the non-charging routes by default. Charging a customer off schedule is treated as an exception that reaches a person, which is what human-in-the-loop means in a billing flow: the machine handles the recovery attempt, and a person owns the decision to take money.

Without FlowRunner

Dunning without a reason A failed charge is retried on a fixed schedule with no read of why it failed
Revenue counted gross The number in the report is the amount charged, and fees and taxes get reconciled separately or late
Local prices converted by hand A base price is turned into local currency in a spreadsheet, at whatever rate was current when someone typed it

With FlowRunner

Dunning that reads the status detail A paused subscription and a failing one are told apart before anything is retried
Revenue counted net The treasury view itemizes fees and taxes, so what reaches the balance is what gets reported
Local prices quoted at a live rate Spot, historical, and time-series rates come from the same platform the payment runs on

Use Case Scenarios

  • Recovering a dead card without touching it

    A renewal fails. Before anything else the agent reads the subscription's status detail, because paused alone does not say whether the customer chose to pause or the payments broke, and defaulted is the state that actually means dunning. For a genuine card failure the agent picks the delivery it wants. Request Card Change hands the conversation to Rebill, which emails the customer directly. Create Card Update Link returns a time-limited hosted URL the agent sends through your own Slack Connect channel, in-app banner, or HubSpot sequence, generated at the moment it is sent rather than stored. When the customer completes it, Rebill emits a card-updated event and the agent knows the fix landed rather than assuming it.

  • A local checkout that is not mistaken for a payment

    A customer in Colombia chooses a bank transfer at checkout. The agent calls APM Checkout, which returns a redirect to complete at their bank and takes no money at all, so a flow that treats the created response as a sale has shipped against nothing. The agent records the expiry, waits for the payment event, and only then releases the entitlement. On the card path it fetches a device id for the customer's country first and passes it into the checkout, because the acquirer's fraud engine uses that to tell a returning customer from a stolen card. It also reads the customer's stored identification documents in advance, rather than discovering at checkout that the method requires one.

  • Month-end reconciliation at the rate that applied

    For every payment in the period the agent calls Get Payment Treasury, which is the only place the fees and taxes are itemized and where the net figure that actually reached the balance appears. Payments taken in a currency other than the reporting one are restated with Get Historical FX Rate for the date they settled, rather than at today's rate. The result is written to Xero and mirrored into Google Sheets for the revenue review, with gross, deductions, and net kept as separate columns so nobody has to reverse-engineer the difference.

Human-in-Loop Highlight

Charge Subscription is the one operation in Rebill's recovery surface that takes money, and it does something else at the same time: it advances the next charge date by one plan frequency. So a retry that runs twice does not just bill the customer twice, it pushes them two cycles forward and quietly desynchronizes their billing anniversary from everyone else's. Meanwhile canceling a subscription is a status change that Rebill does not reverse, so the recovery path and the give-up path are both one-way.

That is why the agent's default in a dunning flow is the card update link, and why the charge is the exception rather than the routine. When an account is still defaulted after the window, the agent posts the case: "Grupo Andina, plan Pro monthly, 2 cycles missed, 184,000 ARS at risk. Card ending 4417 replaced 6 hours ago, card-updated event received. Charge now, or wait for the scheduled renewal in 4 days?" A person answers, because charging a freshly repaired card immediately is a judgment about the relationship, not a rule. The agent never issues that charge twice, and it never cancels a subscription on its own initiative at all.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

77 actions

Customers

7
  • Create Customer Creates a customer. Email is the deduplication key, so an existing address returns the existing record unchanged rather than creating a second one.
  • Get Customer Reads one customer in full, including saved addresses, identification documents, and tokenized cards.
  • List Customers Lists customers with cursor pagination, which is the only route in this API shaped that way.
  • Search Customers Searches customers by free text across names and email with a filter tree, and returns totals that cursor paging does not give you.
  • Update Customer Updates a customer. Changing the email hides their existing cards, since tokens stay with the old address, and metadata replaces rather than merges.
  • List Customer Addresses Lists the addresses saved on one customer.
  • List Customer Identifications Lists the national identity documents on a customer, which several local payment methods will not process without.

Addresses

5
  • Create Address Attaches an address to a customer. Country and state are stored verbatim with no validation, so a typo surfaces later as a declined payment.
  • Get Address Reads one address by id.
  • List Addresses Lists addresses in the organization. Without a customer filter this returns every address on the account.
  • Update Address Updates an address. Every field is optional, so send only what changes.
  • Delete Address Removes an address. One referenced as a card's billing details should stay, since the card is then left without any and address checks fail.

Cards

3
  • Save Card Tokenizes a card into a customer's wallet. This route handles raw card data and puts the flow in scope for card security requirements, which the vendor's browser tokenization exists to avoid.
  • Get Card Reads one saved card. Only the leading digits and last four come back, which is enough to show a customer which card is on file.
  • List Cards Lists the cards saved on a customer. Cards tokenized before an email change no longer appear here, which is vendor behavior rather than an empty wallet.

Checkout

3
  • Card Checkout Charges a card for a one-off payment or to start a subscription. One route covers four shapes: an existing product, an existing plan, an inline amount, or an inline recurrence.
  • APM Checkout Starts a payment through a local alternative method such as a bank transfer. It takes no money and returns a redirect the customer must complete, with the outcome arriving later.
  • Get Device ID Returns a device id and the snippet that generates it, per country. Passing it into a card checkout is what lets the fraud engine recognize a returning customer.

Payments

4
  • Get Payment Reads one payment with its status, amount, method, and the customer behind it.
  • Get Payment Treasury Reads what a payment actually earned: gross, fees, taxes, and the net that reaches your balance. The only place the deductions are itemized.
  • Search Payments Searches payments with free text and a filter tree, returning totals alongside the rows.
  • Refund Payment Refunds a payment in whole or in part. Metadata set at checkout survives the refund, which is what ties it back to your own order.

Products

6
  • Create Product Creates something sold once, as opposed to a plan billed repeatedly. Prices need at least one entry with exactly one marked default.
  • Get Product Reads one product with its prices, status, and archive history.
  • Update Product Updates a product. The price list replaces rather than merges, and existing payment links pointing at it pick up the change.
  • Archive Product Stops a product appearing at checkout while keeping it for reporting. The reversible way to retire something.
  • Unarchive Product Brings an archived product back so it can be sold again.
  • Search Products Lists and searches products. There is no plain listing route, so this search is the list.

Plans

6
  • Create Plan Creates the recurring template a subscription is made from. Trial days and a fixed debit day cannot be combined, and the trial field is only reachable through the API.
  • Get Plan Reads one plan with its frequency, prices, trial, and billing strategy.
  • Update Plan Updates a plan. The price list replaces rather than merges, and the trial and debit day remain mutually exclusive.
  • Archive Plan Stops new subscriptions on a plan. Existing subscriptions keep billing, so archiving closes the door rather than cancelling anyone.
  • Unarchive Plan Brings an archived plan back so it accepts new subscribers.
  • Search Plans Lists and searches plans. As with products, this search is the list.

Payment Links

5
  • Create Payment Link Creates a hosted payment URL for a plan, a product, or a one-off amount. Single use flips the link to expired after the first payment, which is what makes a per-customer invoice link.
  • Get Payment Link Reads one link with its URL, status, prices, and the plan or product behind it.
  • Update Payment Link Updates a link. Setting it active switches a draft on, and setting it expired closes it without deleting the record.
  • Delete Payment Link Deletes a link. Expiring it instead keeps the record and its history.
  • Search Payment Links Lists and searches payment links.

Subscriptions

7
  • Get Subscription Reads one subscription with its status, next charge date, cycle progress, plan, card, and discount. The status detail is what separates a customer pause from a payment failure.
  • Search Subscriptions Lists subscriptions with a rich filter tree. Filtering on the next collection date across a range is what answers what is about to be charged this week.
  • Update Subscription Pauses, resumes, cancels, or reschedules a subscription, since there is no separate cancel route. Cancelling is not reversible.
  • Charge Subscription Charges a subscription immediately, off its schedule. It also advances the next charge date, which is why this page's human gate sits here.
  • Change Subscription Plan Moves a subscription onto a different active plan. Resending the plan it already has emits nothing, so a flow watching for the event simply never fires.
  • Request Card Change Asks Rebill to contact the customer and ask them to update the card behind a subscription, which hands the conversation to the vendor.
  • Create Card Update Link Returns a time-limited hosted URL where a customer replaces their card, so you deliver it however you like. Generate it when you send it.

Coupons

8
  • Create Coupon Creates a discount. A fixed-amount coupon needs an entry for every currency it can be redeemed in, since Rebill will not convert, and applicable cycles is what stops a subscription discount running forever.
  • Get Coupon Reads one coupon with its format, restrictions, redemption count, and status.
  • Update Coupon Updates the editable fields on a coupon. Its id, redemption count, status, and dates are read only.
  • Archive Coupon Stops a coupon being offered while keeping its redemption history. The reversible way to end a promotion.
  • Unarchive Coupon Brings an archived coupon back so it can be redeemed again.
  • Delete Coupon Deletes a coupon permanently, losing the redemption history that archiving keeps.
  • Search Coupons Lists coupons filtered by status, format, plan, and currency.
  • List Applicable Coupons Lists the coupons that would actually be accepted for a plan and currency right now, after every restriction has been applied. What a checkout page should call rather than filtering the full list itself.

Foreign Exchange

5
  • List FX Symbols Lists the currencies the exchange feed supports, which is not the same set your plans and products may be priced in.
  • Get FX Spot Rate Reads today's rate from one currency into others, for pricing a plan in local terms.
  • Convert Amount Converts a specific sum at today's rate. It is a lookup rather than an exchange, and the figure is indicative rather than a locked quote.
  • Get Historical FX Rate Reads the rate as it stood on a past date, which is what a report must use to restate a foreign-currency payment.
  • Get FX Timeseries Reads rates day by day across a range, for a chart or a monthly average.

Organization

1
  • Get Organization Reads the organization a key belongs to, including the alias that appears in every payment link URL. Also the cheapest way to confirm a key works.

Team

8
  • List Members Lists everyone with access, with their roles and whether each is active or still an unaccepted invitation.
  • Get Member Reads one member of the organization.
  • List Roles Lists the roles a member can hold. This route answers without authentication, so it works before a key is configured.
  • Invite Members Invites people by email. They appear as members immediately in an invited state and have no access until they accept.
  • Update Member Role Changes what a team member is allowed to do.
  • Deactivate Member Suspends a member's access without removing them, keeping their history attributed. The reversible way to cut someone off.
  • Activate Member Restores a suspended member's access.
  • Revoke Invitation Withdraws an unaccepted invitation, which is a different operation from deactivating someone who already joined.

Webhooks

9
  • Create Webhook Creates an endpoint, active and receiving immediately. Rebill does not sign its deliveries, so the URL's own secrecy is the defense and an unguessable segment belongs in it.
  • Get Webhook Reads one webhook with its URL, subscribed events, and whether it is active.
  • Update Webhook Updates a webhook. The event list replaces rather than merges, and switching it inactive pauses delivery without deleting the record.
  • Delete Webhook Deletes a webhook. Turning it inactive is the reversible way to stop deliveries.
  • Search Webhooks Lists webhooks with paging, sorting, and a date range.
  • Send Test Event Fires a synthetic event at a webhook so you can exercise your endpoint, including the rejected path that nobody tests until it happens.
  • Get Retry Settings Reads how failed deliveries are retried. After the last attempt Rebill stops and flags the delivery as failed, so nothing arrives later.
  • Update Retry Settings Replaces the retry schedule. It applies organization wide, to every webhook on the account.
  • Reset Retry Settings Puts the retry schedule back to its default, also organization wide.

Triggers

1 triggers

Event Triggers

1
  • On Rebill Event Fires when Rebill reports a payment created or updated, a subscription created or updated, or a subscription due to renew soon. The renewal warning is the one a pre-billing flow wants, because it arrives before the charge rather than after the decline, and the record is lifted out of the vendor's envelope so the flow reads it directly.

Frequently Asked Questions

What can FlowRunner do with Rebill?

FlowRunner agents can run Create Customer, Get Customer, and List Customers in Rebill, plus 74 more actions.

Does connecting Rebill to FlowRunner require OAuth?

No. Rebill connects to FlowRunner with an API key, no OAuth flow required.

Can Rebill trigger a FlowRunner workflow automatically?

Yes. Rebill supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Rebill

Free plan, no card required. Connect in minutes.