The whole subscription stack, for Armenia

Ronda is the software brain on top of your bank's rails. The bank is the vault and moves the money; Ronda decides who to charge, when, how much, and what to do when a card fails.

Start free API reference

The core

Recurring billing that runs itself

A plan is an amount and an interval. A subscription attaches a customer and a saved card to that plan, and from then on Ronda charges it on schedule — merchant-initiated, with no 3-D Secure prompt and nobody present. Trials can start with a card on file or without one. Mid-cycle upgrades charge the prorated difference immediately; downgrades credit the customer and the credit is spent on the next renewal.

Day, week, month and year intervals, with any interval countTrials with or without a card, and a reminder three days before they endUpgrades, downgrades and quantity changes with exact prorationPause and resume without billing the paused gapCancel now or at period end

The differentiator

Failed payments get chased

A failed renewal is usually an expired card, not a lost customer. Ronda retries on a fixed ladder — at failure, then +1, +3 and +5 days — and emails the customer a link to update their card at every step. The Recovery screen shows each attempt, the decline reason and processor code, and when the next attempt runs. Recovered revenue is reported as its own number, because it is often larger than what Ronda costs.

Four attempts, then cancellation, with the customer emailed each timeEvery attempt visible with its decline reason and codeA card updated mid-ladder is charged immediately, not at the next stepRecovered revenue reported separately from ordinary revenue

Customer-facing

Hosted checkout and a self-serve portal

The checkout is mobile-first and carries your name and colour. The card itself is entered on your bank's page and comes back as a token — Ronda never receives a card number, which is what keeps the integration in the lightest PCI tier. Your customers can manage their own subscription from an emailed link: update the card, see their payment history, cancel.

Card, Idram and Telcell on one page3-D Secure on the first payment, handled by the bankPayment links for a fixed amount, a customer-chosen amount, or a planCustomer portal with card update, history and self-cancel

For developers

An API you can actually build on

A REST API with prefixed object ids, integer minor-unit amounts, cursor pagination, one error envelope and an Idempotency-Key on everything that moves money. Test and live modes have separate keys and separate data, so nothing you do while integrating can touch real money. Webhooks are signed with a timestamped HMAC and delivered from an outbox with retries; every delivery can be inspected and replayed from the dashboard.

Publishable and secret keys, per mode, with scopes and rotationIdempotency keys, cursor pagination and metadata on every objectSigned webhooks with replay protection and a full event cataloguePublished test cards for approvals, declines, 3-D Secure and dunning

Running the business

The numbers, and who can touch them

Balance separates what you have collected from what the bank has settled, derived from an append-only ledger rather than a mutable column. Disputes arrive as rows you can respond to. Team members have roles, admins can be required to use two-factor authentication, and every privileged action is written to an audit log.

MRR, revenue, active subscriptions and recovered revenue at a glanceAppend-only ledger, reconcilable against the bankDisputes with evidence deadlinesOwner, admin and viewer roles, TOTP two-factor, session revocation

See it with your own data

Test mode is free and unlimited, with published test cards for every outcome including a decline you can watch dunning recover.

Create your account