How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Vyne website screenshot

Vyne

Vyne was a London-based account-to-account (A2A) open banking payments platform, founded in 2019. It offered merchants real-time pay-by-bank payments, instant refunds, no-code payment links and verified payouts, built on open banking rails and real-time ACH networks with in-app biometric SCA across the UK and Europe. Vyne served retail, financial services and automotive merchants and won Best Open Banking Payments Project at the Open Banking Expo Awards 2023. In September 2024 Vyne was acquired by Dubai-based open banking platform Tarabut, and it wound down its UK operations effective 22 April 2025. The payvyne.com domain has since been repurposed to an unrelated site, and Vyne no longer operates a public developer portal, API reference or OpenAPI surface. This profile is retained as a historical record; there is no live API to enrich.

API Evangelist profiles Vyne the way a machine reads it — 1 machine-readable artifact, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

How we profile Vyne

Each block below is one kind of artifact we hold for Vyne. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

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

Vyne Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Every other property we hold for Vyne — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Access & Security 1

Authentication, authorization, and security posture

Company 1

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/vyne · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Vyne, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.