Nymcard website screenshot

Nymcard

NymCard is a MENA-based, full-stack payments infrastructure provider whose nCore platform gives banks, fintechs and enterprises RESTful APIs to launch and manage card programs. nCore covers card issuing (virtual, physical, prepaid, debit, credit and tokenized cards), user KYC/KYB onboarding, funding and transfers, product management (balance and velocity limits, fees, MCC authorization controls), the full transaction lifecycle, 3D Secure, PCI-compliant PAN handling, webhooks and embedded lending. The platform is PCI DSS Level 1 certified and NymCard is a principal member of both Visa and Mastercard, with offices in London and Dubai. Backed by QED Investors.

Nymcard publishes 1 API on the APIs.io network. Tagged areas include Company, Payments, Card Issuing, Banking as a Service, and Fintech.

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

Nymcard’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, signup flow, authentication, and 20 more developer resources.

47.9/100 developing ▬ flat Agent 27/100 agent aware saas Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
1 APIs
CompanyPaymentsCard IssuingBanking as a ServiceFintechEmbedded FinanceMENA

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/nymcard: 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 1

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

nCore API

RESTful card-issuing and payments platform API for users, cards, card products, accounts, funding/transfers, limits, transactions and webhooks.

Event Specifications 1

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

Security Posture 2

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

Nymcard Authentication

apiKey · 1 scheme

SECURITY

Nymcard Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 2

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 1

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: nymcard
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: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  - sandbox
  generated: '2026-09-03'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/nymcard.png
name: Nymcard
description: NymCard is a MENA-based, full-stack payments infrastructure provider whose nCore platform gives banks, fintechs
  and enterprises RESTful APIs to launch and manage card programs. nCore covers card issuing (virtual, physical, prepaid,
  debit, credit and tokenized cards), user KYC/KYB onboarding, funding and transfers, product management (balance and velocity
  limits, fees, MCC authorization controls), the full transaction lifecycle, 3D Secure, PCI-compliant PAN handling, webhooks
  and embedded lending. The platform is PCI DSS Level 1 certified and NymCard is a principal member of both Visa and Mastercard,
  with offices in London and Dubai. Backed by QED Investors.
url: https://raw.githubusercontent.com/api-evangelist/nymcard/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- qed-investors
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Payments
- Card Issuing
- Banking as a Service
- Fintech
- Embedded Finance
- MENA
apis:
- name: nCore API
  description: RESTful card-issuing and payments platform API for users, cards, card products, accounts, funding/transfers,
    limits, transactions and webhooks.
  humanURL: https://docs.nymcard.com/
  baseURL: https://api.nymcard.com/v1
  properties:
  - type: Documentation
    url: https://docs.nymcard.com/
  - type: APIReference
    url: https://portal.stg.platform.ae-1.nymcard.com/default/documentation/02_api_specs
  - type: GettingStarted
    url: https://docs.nymcard.com/get-started/quick-tutorial
  - type: Authentication
    url: authentication/nymcard-authentication.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DeveloperPortal
  url: https://docs.nymcard.com/
- type: Documentation
  url: https://docs.nymcard.com/
- type: APIReference
  url: https://portal.stg.platform.ae-1.nymcard.com/default/documentation/02_api_specs
- type: GettingStarted
  url: https://docs.nymcard.com/get-started/quick-tutorial
- type: Blog
  url: https://www.nymcard.com/company/blog
- type: Support
  url: https://www.nymcard.com/company/contact
- type: SignUp
  url: https://portal.sand.platform.nymcard.com/default/login
- type: PrivacyPolicy
  url: https://www.nymcard.com/legal/privacy
- type: Postman
  url: https://god.gw.postman.com/run-collection/19938718-ce866362-3acf-4546-8ae4-9b5a15f99811?action=collection%2Ffork&source=rip_markdown
- type: Authentication
  url: authentication/nymcard-authentication.yml
- type: Conventions
  url: conventions/nymcard-conventions.yml
- type: Idempotency
  url: conventions/nymcard-conventions.yml
- type: ErrorCatalog
  url: errors/nymcard-problem-types.yml
- type: DeclineCodes
  url: errors/nymcard-decline-codes.yml
- type: Lifecycle
  url: lifecycle/nymcard-lifecycle.yml
- type: Deprecation
  url: lifecycle/nymcard-lifecycle.yml
- type: ChangeLog
  url: changelog/nymcard-changelog.yml
- type: Conformance
  url: conformance/nymcard-conformance.yml
- type: Compliance
  url: conformance/nymcard-conformance.yml
- type: Webhooks
  url: asyncapi/nymcard-webhooks.yml
- type: Sandbox
  url: sandbox/nymcard-sandbox.yml
- type: X-MCPServerCandidate
  url: mcp/nymcard-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: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/nymcard-llms.txt
- type: WellKnown
  url: well-known/nymcard-well-known.yml
- type: DomainSecurity
  url: security/nymcard-domain-security.yml
- type: Website
  url: http://www.nymcard.com
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 14
  pass: local-v1

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/nymcard"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/nymcard/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/nymcard/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.

A second provider on the same verified email joins the account you already have.