Rotessa

Rotessa is a Winnipeg, Manitoba-based fintech that helps small and mid-sized North American businesses collect recurring payments directly from their customers' bank accounts. In Canada it moves money over the pre-authorized debit (PAD) rails and in the United States over ACH, positioning itself as a low-cost, bank-account-native alternative to card processing for invoices, memberships, subscriptions, tuition, and rent. Rotessa exposes a genuine public REST API (https://api.rotessa.com/v1) that lets platforms and businesses programmatically create customers, verify bank details (including via the Flinks aggregator), and schedule one-time or recurring transactions, backed by a free sandbox (sandbox.rotessa.com) and API-key authentication. As an API-native SMB money-movement fintech, it sits in the thin-but-real account-to-account layer of Canada's payments market, alongside peers like VoPay, Plooto, and Helcim, operating through bank rails and aggregators rather than any live open-banking payment mandate.

Rotessa publishes 3 API contracts indexed on the APIs.io network: Customers API, Transaction Report API, and Transaction Schedules API. Tagged areas include Payments, Canada, Pre-Authorized Debit, ACH, and Account-to-Account.

The Rotessa catalog on APIs.io includes 1 Spectral governance ruleset.

Rotessa’s developer surface includes authentication, documentation, API reference, getting-started guide, pricing, engineering blog, support, and 27 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

36.5/100 thin ▬ flat Agent 24/100 agent aware Front door AI 1/6 silent Heartbeat 19/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessPaid

1 published contract 2 Agent Skills

Payments CanadaPre-Authorized DebitACH Account-to-Account Bank Payments Recurring Payments Subscription Direct Debit Money Movement Open Banking

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Payments & Card Management

BC-1340

Transaction Schedules

POST /transaction_schedules

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 36.5/100 · thin

Contract Quality 10.0 / 19

Developer Ergonomics 5.6 / 15

Access Clarity 5.7 / 15

Operational Transparency 0.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.0 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Banking & Open Finance regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/rotessa/"><img src="https://apis.io/badge/rotessa/card.svg" alt="Rotessa on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document

8 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Operational Transparency scores 2.6 — up to +12.7 composite points
Developer Ergonomics scores 37.5 — up to +12.5 composite points
Access Clarity scores 38.2 — up to +12.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/rotessa/apis.yml: open an issue on github.com/api-evangelist/rotessa to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	10.7	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

NACHA

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 3

Individual APIs this provider publishes, each with its own machine-readable definition.

Rotessa Customers API

Create, retrieve, and update the customers (bank-account holders) that Rotessa withdraws recurring payments from. Supports lookup by Rotessa customer ID or by a merchant-supplie...

Rotessa Transaction Report API

Retrieve financial transaction records and their status (and status reasons) for reconciliation and reporting via the transaction report endpoint. Base URL https://api.rotessa.c...

Rotessa Transaction Schedules API

Create and manage one-time and recurring pre-authorized debit / ACH transaction schedules against a customer's bank account, including schedule frequency, creation by Rotessa cu...

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Rotessa API

OPEN COLLECTION

Agent Skills 2

Packaged agent skills for driving this provider's APIs from an AI assistant.

Onboard a customer and start a recurring debit

AGENT SKILL

Reconcile transactions and handle declines

AGENT SKILL

Rotessa API pricing

Prices published by Rotessa, read 2026-09-20 from rotessa.com/pricing/.

Plan	Price
Base plan	$25/month + $0.50/transaction
1-10 Transactions	$17/mo. Includes: 1-10 transactions
11-50 Transactions	$39/mo. Includes: 11-50 transactions
51-100 Transactions	$65/mo. Includes: 51-100 transactions
101-250 Transactions	$94/mo. Includes: 101-250 transactions
251-1000 Transactions	35¢ per transaction
1001+ Transactions	Custom

Plan details, limits and sources →

Pricing Plans 2

Published pricing tiers and plan structures.

Rotessa Plans Pricing

7 plans

PLANS

Rotessa Price Estimates

0 plans

PLANS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Rotessa

SLA

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Rotessa API Rules

66 rules · 63 errors 2 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Rotessa Openapi Overlay

3 actions · update · rotessa-openapi.yml

DERIVED

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Rotessa Authentication

apiKey · 1 scheme

SECURITY

Rotessa Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Rotessa Agentic Access

13 operations · 8 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

Sandbox

Sandbox

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

OpenAPI

OpenAPI

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 4

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

DeclineCodes

Packages

ToolCrosswalk

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 4

Pricing, plans, and the legal terms of use

Plans

Pricing

TermsOfService

PrivacyPolicy

Company 4

The organization behind the API

BlogRSS

BlogRSS

Website

Website

LinkedIn

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: rotessa
url: https://raw.githubusercontent.com/api-evangelist/rotessa/refs/heads/main/apis.yml
name: Rotessa
kind: company
description: Rotessa is a Winnipeg, Manitoba-based fintech that helps small and mid-sized North American businesses collect
  recurring payments directly from their customers' bank accounts. In Canada it moves money over the pre-authorized debit
  (PAD) rails and in the United States over ACH, positioning itself as a low-cost, bank-account-native alternative to card
  processing for invoices, memberships, subscriptions, tuition, and rent. Rotessa exposes a genuine public REST API (https://api.rotessa.com/v1)
  that lets platforms and businesses programmatically create customers, verify bank details (including via the Flinks aggregator),
  and schedule one-time or recurring transactions, backed by a free sandbox (sandbox.rotessa.com) and API-key authentication.
  As an API-native SMB money-movement fintech, it sits in the thin-but-real account-to-account layer of Canada's payments
  market, alongside peers like VoPay, Plooto, and Helcim, operating through bank rails and aggregators rather than any live
  open-banking payment mandate.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Paid
  confidence: high
  source:
  - plans
  - authentication
  - security
  - sandbox
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- Canada
- Pre-Authorized Debit
- ACH
- Account-to-Account
- Bank Payments
- Recurring Payments
- Subscription
- Direct Debit
- Money Movement
- Open Banking
tags_raw:
- Payments
- Canada
- Pre-Authorized Debit
- ACH
- Account-to-Account
- Bank Payments
- Recurring Payments
- Subscriptions
- Direct Debit
- Money Movement
- Open Banking
created: '2026-07-24'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: rotessa:rotessa-customers-api
  name: Rotessa Customers API
  description: Create, retrieve, and update the customers (bank-account holders) that Rotessa withdraws recurring payments
    from. Supports lookup by Rotessa customer ID or by a merchant-supplied custom identifier, and PATCH or POST update flows.
    Base URL https://api.rotessa.com/v1; API-key authentication.
  humanURL: https://rotessa.com/docs/#customers
  baseURL: https://api.rotessa.com/v1
  tags:
  - Customers
  - Bank Accounts
  properties:
  - type: OpenAPI
    url: openapi/rotessa-customers-api-openapi.yml
  - type: Documentation
    url: https://rotessa.com/docs/#customers
  - type: APIReference
    url: https://rotessa.com/docs/#customers
- aid: rotessa:rotessa-transaction-report-api
  name: Rotessa Transaction Report API
  description: Retrieve financial transaction records and their status (and status reasons) for reconciliation and reporting
    via the transaction report endpoint. Base URL https://api.rotessa.com/v1; API-key authentication.
  humanURL: https://rotessa.com/docs/#transaction-report
  baseURL: https://api.rotessa.com/v1
  tags:
  - Transaction Report
  - Transaction
  - Reporting
  - Reconciliation
  properties:
  - type: OpenAPI
    url: openapi/rotessa-transaction-report-api-openapi.yml
  - type: Documentation
    url: https://rotessa.com/docs/#financial-transactions
  - type: APIReference
    url: https://rotessa.com/docs/#transaction-report
  tags_raw:
  - Transactions
  - Reporting
  - Reconciliation
- aid: rotessa:rotessa-transaction-schedules-api
  name: Rotessa Transaction Schedules API
  description: Create and manage one-time and recurring pre-authorized debit / ACH transaction schedules against a customer's
    bank account, including schedule frequency, creation by Rotessa customer ID or custom identifier, PATCH/POST updates,
    and deletion. Base URL https://api.rotessa.com/v1; API-key authentication.
  humanURL: https://rotessa.com/docs/#transaction-schedules
  baseURL: https://api.rotessa.com/v1
  tags:
  - Transaction Schedules
  - Recurring Payments
  - Pre-Authorized Debit
  properties:
  - type: OpenAPI
    url: openapi/rotessa-transaction-schedules-api-openapi.yml
  - type: Documentation
    url: https://rotessa.com/docs/#transaction-schedules
  - type: APIReference
    url: https://rotessa.com/docs/#transaction-schedules
common:
- url: https://rotessa.com/blog/feed/
  type: BlogRSS
- type: Plans
  url: plans/rotessa-plans-pricing.yml
- type: CapabilityMap
  url: capabilities/rotessa-capability-edges.yml
  name: Rotessa Business Capability Map
- type: AgenticAccess
  url: agentic-access/rotessa-agentic-access.yml
- type: DomainSecurity
  url: security/rotessa-domain-security.yml
- type: Authentication
  url: authentication/rotessa-authentication.yml
- type: Website
  url: https://rotessa.com/
- type: DeveloperPortal
  url: https://rotessa.com/our-customers/developers/
- type: Documentation
  url: https://rotessa.com/docs/
- type: APIReference
  url: https://rotessa.com/docs/
- type: GettingStarted
  url: https://support.rotessa.com/rotessas-sandbox-and-api
- type: GitHubOrganization
  url: https://github.com/Rotessa
- type: LinkedIn
  url: https://www.linkedin.com/company/rotessa
- type: Pricing
  url: https://rotessa.com/pricing/
- type: Blog
  url: https://rotessa.com/blog/
- type: Support
  url: https://support.rotessa.com/
- type: SignUp
  url: https://rotessa.com/sign-up/
- type: Login
  url: https://app.rotessa.com/login
- type: TermsOfService
  url: https://rotessa.com/legal/
- type: PrivacyPolicy
  url: https://rotessa.com/legal/privacy/
- type: OpenAPI
  url: openapi/_original/rotessa-openapi.yml
- type: LLMsTxt
  url: llms/rotessa-llms.txt
- type: Conventions
  url: conventions/rotessa-conventions.yml
- type: ErrorCatalog
  url: errors/rotessa-problem-types.yml
- type: DeclineCodes
  url: errors/rotessa-decline-codes.yml
- type: Lifecycle
  url: lifecycle/rotessa-lifecycle.yml
- type: Sandbox
  url: sandbox/rotessa-sandbox.yml
- type: Conformance
  url: conformance/rotessa-conformance.yml
- type: DataModel
  url: data-model/rotessa-data-model.yml
- type: Packages
  url: packages/rotessa-packages.yml
- type: X-MCPServerCandidate
  url: mcp/rotessa-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ToolCrosswalk
  url: mcp/rotessa-tool-crosswalk.yml
- type: Overlay
  url: overlays/rotessa-openapi-overlay.yaml
- type: AgentSkill
  url: skills/_index.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Rotessa API — frequently asked questions

Does Rotessa have an API?

Yes. APIs.io lists 3 APIs from Rotessa, including Rotessa Customers API, Rotessa Transaction Report API and Rotessa Transaction Schedules API.

Is there an OpenAPI specification for the Rotessa API?

Yes. APIs.io indexes 3 OpenAPI specifications for Rotessa, each linked for download from this page.

How do I authenticate with the Rotessa API?

Rotessa uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Rotessa Authentication.

How much does the Rotessa API cost?

Rotessa publishes its prices; its Base plan plan is $25/month + $0.50/transaction as of 2026-09-20. APIs.io lists 7 pricing plans for Rotessa, with each plan's price, limits and inclusions under Pricing on this page.

Is the Rotessa API ready for AI agents?

Rotessa has a Kin Score of 36.5 out of 100 (thin) and an Agent Readiness score of 23.6 (agent-aware), scored by API Evangelist on 2026-11-06.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/rotessa"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/rotessa/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/rotessa/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.