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 APIs on the APIs.io network. Tagged areas include Payments, Canada, Pre-Authorized Debit, ACH, and Account-to-Account.

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

37.4/100 thin ▬ flat Agent 48/100 agent ready Full breakdown ↓
scored 2026-07-27 · rubric v0.5
3 APIs 1 MCP Servers
PaymentsCanadaPre-Authorized DebitACHAccount-to-AccountBank PaymentsRecurring PaymentsSubscriptionsDirect DebitMoney MovementOpen Banking

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 37.4/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 14.8 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 10.0 / 10
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 0 / 18
Agentic Access Contract 15 / 15
MCP Server 12 / 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
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/rotessa: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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 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...

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...

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

rotessa-mcp.yml

MCP SERVER

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 · 9 acting

13 operations · 9 acting

AGENTIC

Resources

Get Started 5

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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.
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
- Subscriptions
- Direct Debit
- Money Movement
- Open Banking
created: '2026-07-24'
modified: '2026-07-25'
specificationVersion: '0.19'
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: Documentation
    url: https://rotessa.com/docs/#customers
  - type: APIReference
    url: https://rotessa.com/docs/#customers
- 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: Documentation
    url: https://rotessa.com/docs/#transaction-schedules
  - type: APIReference
    url: https://rotessa.com/docs/#transaction-schedules
- 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:
  - Transactions
  - Reporting
  - Reconciliation
  properties:
  - type: Documentation
    url: https://rotessa.com/docs/#financial-transactions
  - type: APIReference
    url: https://rotessa.com/docs/#transaction-report
common:
- 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/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: MCPServer
  url: mcp/rotessa-mcp.yml
- 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