Paystone

Paystone is a Canadian payment processing and customer-engagement company headquartered in London, Ontario, positioning itself as one of the country's largest bank-independent payment processors. It sells card-present terminals, online checkout and hosted payment pages, virtual terminals, invoicing, and recurring billing to Canadian small and mid-sized businesses, and layers loyalty, gift-card, and reputation-marketing products on top of the payment rails. Paystone owns DataCandy, a long-standing Canadian gift-card and loyalty platform, and it is DataCandy that carries Paystone's public, self-serve, documented API surface: a live API Platform (Hydra/JSON-LD) REST API at api.paystone.com covering merchants, clients, contacts, gift/loyalty/ prepaid/promo account types, transactions, member and balance portals, and webhooks, authenticated with JWT bearer tokens and documented through an interactive Swagger UI. Paystone's core card-acquiring and payment-gateway processing is delivered as a merchant product rather than a publicly self-serve developer API, so the honest developer story here is the DataCandy gift-and-loyalty platform API, not a public payments/acquiring API.

Paystone publishes 1 API on the APIs.io network: DataCandy API. Tagged areas include Payments, Canada, Payment Processing, Acquiring, and Gift Cards.

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

Paystone’s developer surface includes authentication, documentation, API reference, pricing, engineering blog, signup flow, and 20 more developer resources.

🌐 Visit website 📡 Source on GitHub
50.7/100 developing ▬ flat Agent 71/100 agent native Full breakdown ↓
scored 2026-07-27 · rubric v0.5
1 APIs 1 MCP Servers
PaymentsCanadaPayment ProcessingAcquiringGift CardsLoyaltySubscriptionsBillingMerchant Services

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 50.7/100 · developing
Contract Quality 16.8 / 25
Developer Ergonomics 11.3 / 20
Commercial Clarity 8.9 / 20
Operational Transparency 3.8 / 13
Governance 0.0 / 12
Discoverability 9.3 / 10
Agent readiness — 71/100 · agent native
Machine-Readable Contract 18 / 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 6 / 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/paystone: 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 1

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

Paystone DataCandy API

The public, documented REST API for Paystone's DataCandy gift-card and loyalty platform, built on API Platform (Hydra/JSON-LD) and served from api.paystone.com. It exposes 28 do...

MCP Servers 1

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

paystone-mcp.yml

MCP SERVER

Event Specifications 1

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

Paystone Datacandy Webhooks

ASYNCAPI

Security Posture 2

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

Paystone Authentication

http · 1 scheme

SECURITY

Paystone Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

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

Paystone Agentic Access

38 operations · 11 acting

38 operations · 11 acting

AGENTIC

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal
DeveloperPortal
 Login
Login
 SignUp
SignUp

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess
 MCPServer
MCPServer
 AgentSkill
AgentSkill
 LLMsTxt
LLMsTxt

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions
Conventions
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conformance
Conformance
 DataModel
DataModel
 Webhooks
Webhooks

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

Authentication
Authentication
 DomainSecurity
DomainSecurity

Operate 2

Status, limits, changes, and where to get help

HelpCenter
HelpCenter
 StatusPage
StatusPage

Commercial 3

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Other 1

Properties that don't map to a standard resource type

Overlay
Overlay

Source (apis.yml)

apis.yml Raw ↑ 
aid: paystone
url: https://raw.githubusercontent.com/api-evangelist/paystone/refs/heads/main/apis.yml
name: Paystone
kind: company
description: 'Paystone is a Canadian payment processing and customer-engagement company headquartered in London, Ontario,
  positioning itself as one of the country''s largest bank-independent payment processors. It sells card-present terminals,
  online checkout and hosted payment pages, virtual terminals, invoicing, and recurring billing to Canadian small and mid-sized
  businesses, and layers loyalty, gift-card, and reputation-marketing products on top of the payment rails. Paystone owns
  DataCandy, a long-standing Canadian gift-card and loyalty platform, and it is DataCandy that carries Paystone''s public,
  self-serve, documented API surface: a live API Platform (Hydra/JSON-LD) REST API at api.paystone.com covering merchants,
  clients, contacts, gift/loyalty/ prepaid/promo account types, transactions, member and balance portals, and webhooks, authenticated
  with JWT bearer tokens and documented through an interactive Swagger UI. Paystone''s core card-acquiring and payment-gateway
  processing is delivered as a merchant product rather than a publicly self-serve developer API, so the honest developer story
  here is the DataCandy gift-and-loyalty platform API, not a public payments/acquiring API.'
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
tags:
- Payments
- Canada
- Payment Processing
- Acquiring
- Gift Cards
- Loyalty
- Subscriptions
- Billing
- Merchant Services
tags_original:
- Payments
- Canada
- Payment Processing
- Gift Cards
- Loyalty
created: '2026-07-24'
modified: '2026-07-24'
specificationVersion: '0.19'
apis:
- aid: paystone:paystone-datacandy-api
  name: Paystone DataCandy API
  description: The public, documented REST API for Paystone's DataCandy gift-card and loyalty platform, built on API Platform
    (Hydra/JSON-LD) and served from api.paystone.com. It exposes 28 documented paths across 14 resource groups — client and
    merchant management, contacts, gift/loyalty/prepaid/promo account types, loyalty and prepaid transactions, rewards and
    items, member and balance portals, user management, and webhook management. All endpoints require a JWT bearer token.
    An interactive Swagger UI is published at api.paystone.com/docs and a machine-readable OpenAPI 3.1 export is downloadable
    from the same host.
  humanURL: https://api.paystone.com/docs
  baseURL: https://api.paystone.com
  tags:
  - Gift Cards
  - Loyalty
  - Prepaid
  - Merchant Management
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/paystone-datacandy-openapi.yml
  - type: Documentation
    url: https://api.paystone.com/docs
  - type: APIReference
    url: https://api.paystone.com/docs
common:
- type: Authentication
  url: authentication/paystone-authentication.yml
- type: AgenticAccess
  url: agentic-access/paystone-agentic-access.yml
- type: DomainSecurity
  url: security/paystone-domain-security.yml
- type: Conventions
  url: conventions/paystone-conventions.yml
- type: ErrorCatalog
  url: errors/paystone-problem-types.yml
- type: Lifecycle
  url: lifecycle/paystone-lifecycle.yml
- type: Conformance
  url: conformance/paystone-conformance.yml
- type: DataModel
  url: data-model/paystone-data-model.yml
- type: MCPServer
  url: mcp/paystone-mcp.yml
- type: Webhooks
  url: asyncapi/paystone-datacandy-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/paystone-llms.txt
- type: Overlay
  url: overlays/paystone-datacandy-overlay.yaml
- type: Website
  url: https://www.paystone.com/
- type: DeveloperPortal
  url: https://api.paystone.com/docs
- type: Documentation
  url: https://api.paystone.com/docs
- type: APIReference
  url: https://api.paystone.com/docs
- type: Pricing
  url: https://www.paystone.com/pricing
- type: Blog
  url: https://www.paystone.com/resources
- type: HelpCenter
  url: https://help.paystone.com/
- type: StatusPage
  url: https://status.paystone.com
- type: Login
  url: https://hub.paystone.com/login
- type: SignUp
  url: https://start.paystone.com/sign-up
- type: TermsOfService
  url: https://www.paystone.com/legal
- type: PrivacyPolicy
  url: https://www.paystone.com/legal
- type: GitHubOrganization
  url: https://github.com/Paystone
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com