Versapay

Versapay is a Toronto, Canada based B2B payments company focused on accounts receivable (AR) automation and integrated payment acceptance for suppliers and their buyers. Its "Collaborative AR" platform combines electronic invoicing, customer collaboration, cash application, and embedded payment processing so businesses can invoice, get paid, and reconcile inside one workflow, with ERP-adjacent integrations for order-to-cash. Versapay serves the North American mid-market and enterprise segment and, unlike consumer money-movement players in Canada's Interac-dominated market, sits in the API-native B2B acquiring and AR/AP money-movement layer. Its API posture is genuinely public and honest: developers.versapay.com hosts a Redocly-rendered reference for a broad REST platform API (onboarding, wallets, orders, order transactions, gift cards, card-present EMV, settlement reporting, autopay, customers, invoices, divisions, notifications, and webhooks) plus a separate hosted-iframe Ecommerce API for PCI-reduced payment sessions. Authentication is HTTPS Basic access authentication using an API Token and Key issued from the account console, with a UAT sandbox alongside production and a documented webhook event model.

Versapay publishes 22 APIs on the APIs.io network, including Agreements API, Authentication API, Autopay API, and 19 more. Tagged areas include Payments, Canada, Accounts Receivable, AR Automation, and Order-to-Cash.

The Versapay catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Versapay’s developer surface includes authentication, sandbox, documentation, API reference, engineering blog, signup flow, and 26 more developer resources.

🌐 Visit website 📡 Source on GitHub

57.4/100 strong ▬ flat Agent 43/100 agent ready saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

AccessSelf serve

2 APIs

Payments Canada Accounts ReceivableAR AutomationOrder-to-Cash Payment Acceptance Payment Processing B2B Payments Invoicing E-Commerce Card Present Webhook

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 57.4/100 · strong

Contract Quality 10.7 / 19

Developer Ergonomics 7.4 / 15

Access Clarity 6.3 / 15

Operational Transparency 4.1 / 10

Contract Governance 1.6 / 9

Discoverability 5.7 / 8

Regulatory Posture 11.3 / 15

Create-or-Update Ergonomics 3.9 / 10

Agent readiness — 43/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 6 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 6 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Payments 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/.

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 github.com/api-evangelist/versapay: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 22

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

Versapay Agreements API

The Agreements API from Versapay — 7 operation(s) for agreements.

Versapay Authentication API

Visit your account settings in `UAT` (https://uat.versapay.com/account) or `Production` (https://secure.versapay.com/account) to setup API credentials needed for authentication ...

Versapay Autopay API

Autopays are a digital analog to paper pre-authorized debit agreements that businesses could use, for instance, for monthly billing.

Versapay Card Present EMV API

Card Present EMV payment transactions require a Versapay certified point-of-sale terminal. Contact support@versapay.com for support & setup for POS/CP EMV enablement.

Versapay Collaboration API

As a supplier your customers collaborate with you through comments about invoices and/or payments.

Versapay Customers API

As a supplier your customers are the entities that are invoiced. ## Webhooks When using Webhooks, your application will be notified when key events are triggered for a customer.

Versapay Developers API

Operations available to developers

Versapay Divisions API

As a supplier divisions are used to group your invoices.

Versapay File Imports API

As a supplier you can upload customer, invoice, and payment data in CSV file formats.

Versapay Fund Sources API

The Fund Sources API from Versapay — 2 operation(s) for fund sources.

Versapay Gift Cards API

Provisioned gift cards can be activated/enabled (or deactivated/disabled) as well as have their balances loaded/re-loaded with an amount. Contact support@versapay.com for suppor...

Versapay Internal API

Operations intended only to the iframe front end

Versapay Invoices API

As a supplier invoices are your receivables. ## Webhooks When using Webhooks, your application will be notified when key events are triggered for an invoice.

Versapay Invoicing Payments API

As a supplier a payments are made by customers for invoices issued to them. ## Webhooks When using Webhooks, your application will be notified when key events are triggered for ...

Versapay Notifications API

As a supplier you can notify customers about their invoices.

Versapay Onboarding API

Onboarding supports the automated process of applying for merchant services. Contact support@versapay.com for support & setup of supplier onboarding partner credentials.

Versapay Order Transactions API

Order-based card/ACH and card present EMV payment transactions include verify, authorize, capture, sale, void, return refund, and return credit transaction types. If participati...

Versapay Orders API

The Order entity represents the sales document in the ERP system. The fields in the ERP system should be aligned as closely as possible with the fields in the order entity, as t...

Versapay Reference Data API

For convenience purposes only, Versapay can supply third party reference data to its partners and users. This data can be used to implement client-side tooling (e.g., fraud miti...

Versapay Settlement Reporting API

Settlement Reporting includes retrieval of monthly statements, daily deposit amounts (including fee information), transaction exceptions (ACH reject/return & CC chargeback), and...

Versapay Transactions API

The Transactions API from Versapay — 4 operation(s) for transactions.

Versapay Wallets API

The Wallet entity holds vaulted & secured payment methods owned by a customer (buyer/payor) that can be used to make payments via Collaborative AR (online Portals, AutoPay, Pay ...

Scroll for all 22

Open Collections 2

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

Versapay API Reference

OPEN COLLECTION

Versapay Ecommerce API

OPEN COLLECTION

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Versapay Webhooks

ASYNCAPI

Security Posture 2

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

Versapay Authentication

http/oauth2/openIdConnect · 4 schemes

SECURITY

Versapay Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Versapay Scopes

5 scopes · authorizationCode/clientCredentials/password

5 scopes

SCOPES

Agentic Access 1

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

Versapay Agentic Access

106 operations · 54 acting · 2 human-in-the-loop

106 operations · 54 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

Sandbox

Sandbox

DeveloperPortal

DeveloperPortal

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess

AgenticAccess

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

Components

DataModel

Webhooks

Scroll for all 7

Build 1

SDKs, sample code, and the tooling you integrate with

DeclineCodes

DeclineCodes

Access & Security 5

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Compliance

Security

Operate 2

Status, limits, changes, and where to get help

Deprecation

Deprecation

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 3

The organization behind the API

Website

Website

Blog

Blog

LinkedIn

Other 2

Properties that don't map to a standard resource type

Overlay

Overlay

Overlay

Overlay

Source (apis.yml)

aid: versapay
url: https://raw.githubusercontent.com/api-evangelist/versapay/refs/heads/main/apis.yml
name: Versapay
kind: company
description: 'Versapay is a Toronto, Canada based B2B payments company focused on accounts receivable (AR) automation and
  integrated payment acceptance for suppliers and their buyers. Its "Collaborative AR" platform combines electronic invoicing,
  customer collaboration, cash application, and embedded payment processing so businesses can invoice, get paid, and reconcile
  inside one workflow, with ERP-adjacent integrations for order-to-cash. Versapay serves the North American mid-market and
  enterprise segment and, unlike consumer money-movement players in Canada''s Interac-dominated market, sits in the API-native
  B2B acquiring and AR/AP money-movement layer. Its API posture is genuinely public and honest: developers.versapay.com hosts
  a Redocly-rendered reference for a broad REST platform API (onboarding, wallets, orders, order transactions, gift cards,
  card-present EMV, settlement reporting, autopay, customers, invoices, divisions, notifications, and webhooks) plus a separate
  hosted-iframe Ecommerce API for PCI-reduced payment sessions. Authentication is HTTPS Basic access authentication using
  an API Token and Key issued from the account console, with a UAT sandbox alongside production and a documented webhook event
  model.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- Canada
- Accounts Receivable
- AR Automation
- Order-to-Cash
- Payment Acceptance
- Payment Processing
- B2B Payments
- Invoicing
- E-Commerce
- Card Present
- Webhook
tags_raw:
- Payments
- Canada
- Accounts Receivable
- AR Automation
- Order to Cash
- Payment Acceptance
- Payment Processing
- B2B Payments
- Invoicing
- Ecommerce
- Card Present
- Webhooks
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.23'
apis:
- aid: versapay:versapay-agreements-api
  name: Versapay Agreements API
  description: The Agreements API from Versapay — 7 operation(s) for agreements.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Agreements
  properties:
  - type: OpenAPI
    url: openapi/versapay-agreements-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-authentication-api
  name: Versapay Authentication API
  description: 'Visit your account settings in `UAT` (https://uat.versapay.com/account) or `Production` (https://secure.versapay.com/account)
    to setup API credentials needed for authentication as well as webhooks to receive relevant callbacks from Versapay transaction
    processing.


    You can generate/disable your API credentials as often as necessary for security reasons.


    If you do not have an account, please contact Versapay Support for support & setup of AR invoicing integration, hosted
    checkout and/or payment acceptance for partner and/or API credential setup.


    ## API Token and API Key

    API requests are authenticated using `API Token & Key` via [HTTPS Basic Access Authentication](https://en.wikipedia.org/wiki/Basic_access_authentication).
    <table class="security-details"><tbody><tr><th> Security Scheme Type </th><td> <!-- -->HTTPS<!-- --> </td></tr><tr><th>
    HTTPS Authorization Scheme </th><td> <!-- -->basic<!-- --> </td></tr></tbody></table>


    Simply provide the `API Token & Key` values as the `user` and `password` parameters, using cURL for instance:


    `curl -u "Nvax...:UN0I..." -X POST https://secure.versapay.com/api/...`


    ## JWT Token

    Alternatively, API requests can also be authenticated using `JWT Token` via [HTTPS Bearer Authentication](https://en.wikipedia.org/wiki/JSON_Web_Token).
    <table class="security-details"><tbody><tr><th> Security Scheme Type </th><td> <!-- -->HTTPS<!-- --> </td></tr><tr><th>
    HTTP Authorization Scheme </th><td> <!-- -->bearer JWT<!-- --> </td></tr></tbody></table>

    `JWT Tokens`, automatically generated alongside `API Token & Key`, are displayed along with expiration in account settings
    as well as via authenticated `/api/whoami`, see `Authentication` _Echo identity and account profile settings_


    Simply provide the `JWT Token` in the authorization header, using cURL for instance:


    `curl -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0b2tlbiI6Im54eDFaSjgzeXRNNmhtb3NGVExCIiwiZXhwIjoxNzEyOTU5NDA5fQ.adV6U1vW69Ypskt61uPL8hZ-4muvtM4FLM48QN6iCc4"
    -X POST https://secure.versapay.com/api/...`'
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/versapay-authentication-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-autopay-api
  name: Versapay Autopay API
  description: Autopays are a digital analog to paper pre-authorized debit agreements that businesses could use, for instance,
    for monthly billing.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - AutoPay
  tags_raw:
  - Autopay
  properties:
  - type: OpenAPI
    url: openapi/versapay-autopay-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-card-present-emv-api
  name: Versapay Card Present EMV API
  description: Card Present EMV payment transactions require a Versapay certified point-of-sale terminal. Contact support@versapay.com
    for support & setup for POS/CP EMV enablement.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Card Present EMV
  properties:
  - type: OpenAPI
    url: openapi/versapay-card-present-emv-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-collaboration-api
  name: Versapay Collaboration API
  description: As a supplier your customers collaborate with you through comments about invoices and/or payments.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Collaboration
  properties:
  - type: OpenAPI
    url: openapi/versapay-collaboration-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-customers-api
  name: Versapay Customers API
  description: 'As a supplier your customers are the entities that are invoiced.


    ## Webhooks


    When using Webhooks, your application will be notified when key events are triggered for a customer.'
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Customers
  properties:
  - type: OpenAPI
    url: openapi/versapay-customers-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-developers-api
  name: Versapay Developers API
  description: Operations available to developers
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Developers
  tags_raw:
  - developers
  properties:
  - type: OpenAPI
    url: openapi/versapay-developers-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-divisions-api
  name: Versapay Divisions API
  description: As a supplier divisions are used to group your invoices.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Divisions
  properties:
  - type: OpenAPI
    url: openapi/versapay-divisions-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-file-imports-api
  name: Versapay File Imports API
  description: As a supplier you can upload customer, invoice, and payment data in CSV file formats.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - File Imports
  properties:
  - type: OpenAPI
    url: openapi/versapay-file-imports-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-fund-sources-api
  name: Versapay Fund Sources API
  description: The Fund Sources API from Versapay — 2 operation(s) for fund sources.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Fund Sources
  properties:
  - type: OpenAPI
    url: openapi/versapay-fund-sources-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-gift-cards-api
  name: Versapay Gift Cards API
  description: Provisioned gift cards can be activated/enabled (or deactivated/disabled) as well as have their balances loaded/re-loaded
    with an amount. Contact support@versapay.com for support & setup for Gift Card acceptance.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Gift Cards
  properties:
  - type: OpenAPI
    url: openapi/versapay-gift-cards-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-internal-api
  name: Versapay Internal API
  description: Operations intended only to the iframe front end
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Internal
  tags_raw:
  - internal
  properties:
  - type: OpenAPI
    url: openapi/versapay-internal-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-invoices-api
  name: Versapay Invoices API
  description: 'As a supplier invoices are your receivables.


    ## Webhooks


    When using Webhooks, your application will be notified when key events are triggered for an invoice.'
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Invoices
  properties:
  - type: OpenAPI
    url: openapi/versapay-invoices-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-invoicing-payments-api
  name: Versapay Invoicing Payments API
  description: 'As a supplier a payments are made by customers for invoices issued to them.


    ## Webhooks


    When using Webhooks, your application will be notified when key events are triggered for a payment.'
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Invoicing Payments
  properties:
  - type: OpenAPI
    url: openapi/versapay-invoicing-payments-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-notifications-api
  name: Versapay Notifications API
  description: As a supplier you can notify customers about their invoices.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Notification
  tags_raw:
  - Notifications
  properties:
  - type: OpenAPI
    url: openapi/versapay-notifications-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-onboarding-api
  name: Versapay Onboarding API
  description: Onboarding supports the automated process of applying for merchant services. Contact support@versapay.com for
    support & setup of supplier onboarding partner credentials.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Onboarding
  properties:
  - type: OpenAPI
    url: openapi/versapay-onboarding-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-order-transactions-api
  name: Versapay Order Transactions API
  description: 'Order-based card/ACH and card present EMV payment transactions include verify, authorize, capture, sale, void,
    return refund, and return credit transaction types. If participating in a gift card program, gift cards can be used in
    sale, void, refund transaction types. Contact support@versapay.com for support & setup for Order Transactions enablement.

    ## Credit Card Payments

    There are two types of credit card payments: sale and delayed capture. Sale payments occur when the merchant wishes to
    accept a payment for goods or services that have already been shipped or provided to the cardholder. A sale is a financial
    transaction, and the movement of funds will be initiated in response to a sale request. Delayed capture payments are used
    when there is a separation between accepting an order and fulfilling that order. With delayed capture, the credit card
    is first authorized for the estimated order total. The authorization reserves funds on the cardholder’s account for the
    merchant but does not initiate a movement of funds. Once the products or services are ready to be delivered to the cardholder,
    the authorization is captured for the final amount. The capture request initiates the movement of funds.

    ## ACH Payments

    ACH payments are bank-to-bank transfers of funds. Unlike credit card payments, ACH payments only have one type – sale,
    and there is no prior authorization. Therefore, sale amounts are final and cannot be adjusted after the fact. ACH payments
    assume success, and if there is a problem with the funding source, like with a bounced paper check, the originator will
    be notified of a rejection several days after the payment attempt.

    ## EFT Payments

    EFT payments are bank-to-bank transfers of funds. Unlike credit card payments, EFT payments only have one type – sale,
    and there is no prior authorization. Therefore, sale amounts are final and cannot be adjusted after the fact. EFT payments
    assume success, and if there is a problem with the funding source, like with a bounced paper check, the originator will
    be notified of a rejection several days after the payment attempt.

    ## Gift Card Payments

    Provisioned gift cards can be activated/enabled (or deactivated/disabled) as well as have their balances loaded/re-loaded
    with an amount. Contact support@versapay.com for support & setup for Gift Card acceptance.

    ## Point-of-Sale/Card Present EMV Payments

    Card Present EMV payment transactions require a Versapay certified point-of-sale terminal. In addition to the card not
    present transaction types, the following payment transaction types are also supported: device setup, request signature,
    and cancel. Contact support@versapay.com for support & setup for POS/CP EMV enablement.'
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Order Transactions
  properties:
  - type: OpenAPI
    url: openapi/versapay-order-transactions-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-orders-api
  name: Versapay Orders API
  description: The Order entity represents the sales document in the ERP system. The fields in the ERP system should be aligned
    as closely as possible with the fields in the order entity, as the gateway will use these fields for credit card interchange
    optimization. Contact support@versapay.com for support & setup for Order and/or Order Transactions enablement.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Order
  tags_raw:
  - Orders
  properties:
  - type: OpenAPI
    url: openapi/versapay-orders-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-reference-data-api
  name: Versapay Reference Data API
  description: For convenience purposes only, Versapay can supply third party reference data to its partners and users. This
    data can be used to implement client-side tooling (e.g., fraud mitigation services), but it may not be redistributed.
    The accuracy and completeness of this third party data cannot be guaranteed and is for informational and convenience purposes
    only. Contact support@versapay.com for eligibility for reference data enablement.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Reference Data
  properties:
  - type: OpenAPI
    url: openapi/versapay-reference-data-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-settlement-reporting-api
  name: Versapay Settlement Reporting API
  description: Settlement Reporting includes retrieval of monthly statements, daily deposit amounts (including fee information),
    transaction exceptions (ACH reject/return & CC chargeback), and transaction details. Contact support@versapay.com for
    payment acceptance onboarding support & setup and eligibility for Settlement Reporting enablement.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Settlement Reporting
  properties:
  - type: OpenAPI
    url: openapi/versapay-settlement-reporting-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-transactions-api
  name: Versapay Transactions API
  description: The Transactions API from Versapay — 4 operation(s) for transactions.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Transaction
  tags_raw:
  - Transactions
  properties:
  - type: OpenAPI
    url: openapi/versapay-transactions-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
- aid: versapay:versapay-wallets-api
  name: Versapay Wallets API
  description: The Wallet entity holds vaulted & secured payment methods owned by a customer (buyer/payor) that can be used
    to make payments via Collaborative AR (online Portals, AutoPay, Pay Now), Order Transactions (Ecomm & ERP based suppliers),
    and Invoicing Payments (via Partner buyer networks including Virtual Card Connect). Contact support@versapay.com for support
    & setup for Wallet access and payment transaction enablement in relation to licensed product components.
  humanURL: https://developers.versapay.com/
  baseURL: https://secure.versapay.com
  tags:
  - Wallets
  properties:
  - type: OpenAPI
    url: openapi/versapay-wallets-api-openapi.yml
  - type: Documentation
    url: https://developers.versapay.com/
  - type: APIReference
    url: https://developers.versapay.com/
  - type: ToolCrosswalk
    url: mcp/versapay-tool-crosswalk.yml
  - type: Documentation
    url: https://developers.versapay.com/ecommerce/
  - type: APIReference
    url: https://developers.versapay.com/ecommerce/
common:
- type: Overlay
  url: overlays/versapay-api-reference-overlay.yaml
- type: Overlay
  url: overlays/versapay-ecommerce-api-overlay.yaml
- type: AgenticAccess
  url: agentic-access/versapay-agentic-access.yml
- type: DomainSecurity
  url: security/versapay-domain-security.yml
- type: Authentication
  url: authentication/versapay-authentication.yml
- type: OAuthScopes
  url: scopes/versapay-scopes.yml
- type: WellKnown
  url: well-known/versapay-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/versapay-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: LLMsTxt
  url: llms/versapay-llms.txt
- type: Conventions
  url: conventions/versapay-conventions.yml
- type: ErrorCatalog
  url: errors/versapay-problem-types.yml
- type: DeclineCodes
  url: errors/versapay-decline-codes.yml
- type: Lifecycle
  url: lifecycle/versapay-lifecycle.yml
- type: Deprecation
  url: lifecycle/versapay-lifecycle.yml
- type: Conformance
  url: conformance/versapay-conformance.yml
- type: Compliance
  url: https://versapay.com/security
- type: Sandbox
  url: sandbox/versapay-sandbox.yml
- type: Components
  url: components/versapay-components.yml
- type: DataModel
  url: data-model/versapay-data-model.yml
- type: Webhooks
  url: asyncapi/versapay-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Website
  url: https://versapay.com
- type: DeveloperPortal
  url: https://developers.versapay.com/
- type: Documentation
  url: https://developers.versapay.com/
- type: APIReference
  url: https://developers.versapay.com/
- type: StatusPage
  url: https://status.versapay.com
- type: Blog
  url: https://versapay.com/blog
- type: SignUp
  url: https://secure.versapay.com/account
- type: TermsOfService
  url: https://versapay.com/terms
- type: PrivacyPolicy
  url: https://versapay.com/legal/privacy-policy
- type: Security
  url: https://versapay.com/security
- type: LinkedIn
  url: https://www.linkedin.com/company/versapay
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

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/versapay"

All providers

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

Every operation they expose

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

How their score was established

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

Discovery needs no key. Ratings and market analysis are Pro.

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.