# WayPay

**Canonical:** https://apis.io/providers/waypay/  
**Website:** https://waypay.ca  
**APIs profiled:** 0

WayPay was a cloud-based B2B payments and accounts-payable-automation fintech headquartered in Burlington, Ontario, Canada. Its platform let businesses pay any supplier by any method (EFT, cheque, credit card, wire) from a single dashboard, reconciling against accounting and ERP software to automate the accounts-payable workflow. Royal Bank of Canada (RBC) announced its acquisition of WayPay in July 2019, after which the independent brand was retired. As of this enrichment pass the domain waypay.ca resolves via DNS (behind Akamai, enterprise mail) but serves no public site (HTTP 503), and there is no reachable public developer portal, API, or documentation surface.

## Kin Score — 1.5 / 100 (minimal)

Scored 2026-08-20 under rubric 0.12.0. Trend: flat (+0.0 from 1.5).

| Facet | Score |
|---|---|
| Discoverability | 50.0 |
| Contract Quality | 0.0 |
| Governance | 0.0 |
| Contract Governance | 0.0 |
| Operational Transparency | 0.0 |
| Developer Ergonomics | 0.0 |
| Commercial Clarity | 0.0 |
| Access Clarity | 0.0 |

Regulatory layer — **Payments**: 9.4 (matched via tags).

## Agent readiness — 0.0 (human-only)

| Dimension | Value |
|---|---|
| Spec Presence | no |
| Agentic Access | no |
| Reversibility Documented | no |
| MCP Server | no |
| Auth Clarity | no |
| Idempotency | no |
| Error Semantics | no |
| OpenAPI Examples | no |
| Rate Limit Signal | no |
| Event Surface Described | no |
| Agent Skills | no |
| Well Known Catalog | no |
| Consent Identity | no |
| Agent Card | no |
| Dry Run Mode | no |

## Access

Unknown — onboarding: unknown, pricing: unknown, trial: no (confidence: low).

## Security (1)

- **Waypay Domain Security** — no transport/DNS hardening detected

## Tags

Company, Payments, Fintech, Accounts Payable, B2B, Canada, Financial-Services, Acquired

---

Profiled by [API Evangelist](https://apievangelist.com) and published on [APIs.io](https://apis.io/providers/waypay/). Scores are computed from the provider's own public artifacts under a published rubric.