Citcon

Citcon is a global payment processing platform, founded in 2015 and headquartered in San Jose, California, that unifies 100+ local and global payment methods behind a single Universal Payment Interface (UPI) API. Merchants use Citcon to accept digital wallets (Alipay, WeChat Pay, PayPal, Venmo, CashApp, China UnionPay, Kakao Pay, NaverPay, Line Pay, PayPay and more), cards, and Buy Now Pay Later, plus global payouts, pay-by-link, surcharging, dual pricing, and in-store/POS acceptance across 50+ countries and 10+ settlement currencies. The UPI API is a REST/JSON payments API using Bearer access-token authentication with charge, capture, refund, cancel, vault (tokenization), inquiry, and consult operations, IPN webhooks, and a sandbox environment. Citcon is backed by Norwest Venture Partners and Sierra Ventures.

Citcon is listed with 1 API on the APIs.io network. Tagged areas include Company, Payments, Cross-Border Payments, Digital Wallet, and Payment Gateway.

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

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

🌐 Visit website 📡 Profile data on GitHub

47.5/100 developing ▬ flat Agent 27/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-10-31 · rubric v0.25.0 · Show this score on your site →

1 API 1 Agent Skills

Company Payments Cross-Border Payments Digital Wallet Payment Gateway Buy Now Pay Later Global Payouts Fintech

Kin Score

Kin Score How this is scored →
scored 2026-10-31 · rubric v0.25.0

Composite quality — 47.5/100 · developing

Contract Quality 8.3 / 21

Developer Ergonomics 12.4 / 17

Access Clarity 7.2 / 17

Operational Transparency 3.2 / 11

Contract Governance 1.9 / 10

Discoverability 5.6 / 9

Regulatory Posture 5.1 / 15

Agent readiness — 27/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 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

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/citcon/"><img src="https://apis.io/badge/citcon/card.svg" alt="Citcon on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

7 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 39.0 — up to +15.3 composite points
Access Clarity scores 42.1 — up to +11.6 composite points
Contract Governance scores 18.2 — up to +9.8 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/citcon/apis.yml: open an issue on github.com/api-evangelist/citcon to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Consumer Lending Licensing (UK, US, Canada credit licence registers)	regulated	19.2 (thin)	-	-
Canada RPAA Payment Service Providers (Bank of Canada registry + Payments Canada)	regulated	19.2 (thin)	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

APIs 1

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

Citcon Universal Payment Interface (UPI) API

Citcon's UPI is a REST/JSON payments API for accepting 100+ global payment methods. It uses Bearer access-token authentication and exposes charge, charge-confirm, capture, refun...

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Charge and capture a payment with Citcon UPI

AGENT SKILL

Event Specifications 1

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

Citcon Upi Webhooks

ASYNCAPI

Security Posture 2

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

Citcon Authentication

http · 1 scheme

SECURITY

Citcon Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Get Started 4

Portal, sign-up, and the first successful call

DeveloperPortal

GettingStarted

SignUp

Sandbox

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conventions

Idempotency

ErrorCatalog

Lifecycle

Conformance

Webhooks

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 3

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Compliance

Compliance

Authentication

Authentication

Operate 2

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

Commercial 2

Pricing, plans, and the legal terms of use

TermsOfService

TermsOfService

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: citcon
name: Citcon
description: Citcon is a global payment processing platform, founded in 2015 and headquartered in San Jose, California, that
  unifies 100+ local and global payment methods behind a single Universal Payment Interface (UPI) API. Merchants use Citcon
  to accept digital wallets (Alipay, WeChat Pay, PayPal, Venmo, CashApp, China UnionPay, Kakao Pay, NaverPay, Line Pay, PayPay
  and more), cards, and Buy Now Pay Later, plus global payouts, pay-by-link, surcharging, dual pricing, and in-store/POS acceptance
  across 50+ countries and 10+ settlement currencies. The UPI API is a REST/JSON payments API using Bearer access-token authentication
  with charge, capture, refund, cancel, vault (tokenization), inquiry, and consult operations, IPN webhooks, and a sandbox
  environment. Citcon is backed by Norwest Venture Partners and Sierra Ventures.
url: https://raw.githubusercontent.com/api-evangelist/citcon/refs/heads/main/apis.yml
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://cdn.prod.website-files.com/6828b564a444ee6676dd6111/6828b564a444ee6676dd611d_citcon-logo.svg
x-type: company
x-source: vc-portfolio
x-backed-by:
- norwest-venture-partners
- sierra-ventures
x-tier: enriched
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Payments
- Cross-Border Payments
- Digital Wallet
- Payment Gateway
- Buy Now Pay Later
- Global Payouts
- Fintech
tags_raw:
- Company
- Payments
- Cross-Border Payments
- Digital Wallets
- Payment Gateway
- BNPL
- Global Payouts
- Fintech
apis:
- name: Citcon Universal Payment Interface (UPI) API
  description: Citcon's UPI is a REST/JSON payments API for accepting 100+ global payment methods. It uses Bearer access-token
    authentication and exposes charge, charge-confirm, capture, refund, cancel, transaction inquiry, vault (tokenized payment
    methods), and consult operations, plus IPN webhooks for asynchronous payment-status notifications. A sandbox environment
    is available for testing.
  humanURL: https://www.citcon.com/dev/universal-payment-interface-upi---api
  baseURL: https://api.citconpay.com/v1/
  tags:
  - Payments
  - Cross-Border Payments
  - Digital Wallet
  tags_raw:
  - Payments
  - Cross-Border Payments
  - Digital Wallets
  properties:
  - type: Documentation
    url: https://www.citcon.com/dev/universal-payment-interface-upi---api
  - type: APIReference
    url: https://www.citcon.com/dev/universal-payment-interface-upi---api
  - type: Authentication
    url: authentication/citcon-authentication.yml
  - type: Sandbox
    url: sandbox/citcon-sandbox.yml
  - type: Webhooks
    url: asyncapi/citcon-upi-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: DomainSecurity
  url: security/citcon-domain-security.yml
- type: Website
  url: https://citcon.com
- type: DeveloperPortal
  url: https://www.citcon.com/dev/overview
- type: Documentation
  url: https://www.citcon.com/dev/universal-payment-interface-upi---api
- type: APIReference
  url: https://www.citcon.com/dev/universal-payment-interface-upi---api
- type: GettingStarted
  url: https://www.citcon.com/dev/overview
- type: Blog
  url: https://www.citcon.com/resources/blogs-press-releases
- type: Support
  url: https://www.citcon.com/contact
- type: SignUp
  url: https://www.citcon.com/contact
- type: TermsOfService
  url: https://www.citcon.com/terms-conditions
- type: PrivacyPolicy
  url: https://www.citcon.com/privacy-policy
- type: GitHubOrganization
  url: https://github.com/citcon
- type: StatusPage
  url: https://status.citconpay.com
- type: Compliance
  url: https://www.citcon.com/resources/compliance
- type: Authentication
  url: authentication/citcon-authentication.yml
- type: Conventions
  url: conventions/citcon-conventions.yml
- type: Idempotency
  url: conventions/citcon-conventions.yml
- type: ErrorCatalog
  url: errors/citcon-problem-types.yml
- type: Sandbox
  url: sandbox/citcon-sandbox.yml
- type: Lifecycle
  url: lifecycle/citcon-lifecycle.yml
- type: Conformance
  url: conformance/citcon-conformance.yml
- type: Packages
  url: packages/citcon-packages.yml
- type: SDKs
  url: packages/citcon-packages.yml
- type: X-MCPServerCandidate
  url: mcp/citcon-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: Webhooks
  url: asyncapi/citcon-upi-webhooks.yml
- type: LLMsTxt
  url: llms/citcon-llms.txt
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

Citcon API — frequently asked questions

Does Citcon have an API?

Yes. APIs.io lists 1 API from Citcon, including Citcon Universal Payment Interface (UPI) API.

How do I authenticate with the Citcon API?

Citcon uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Citcon Authentication.

Is the Citcon API ready for AI agents?

Citcon has a Kin Score of 47.5 out of 100 (developing) and an Agent Readiness score of 26.8 (agent-aware), scored by API Evangelist on 2026-10-31.

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

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/citcon/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.