Skip to content

Repository files navigation

2C2P (2c2p)

About this repository

This is not our API. This repository is an independent, third-party profile of a company's publicly available API surface, maintained by API Evangelist. API Evangelist does not operate, host, resell, or support this company's APIs, and is not affiliated with or endorsed by the company unless stated on the profile.

Where the information came from. Everything here is assembled from material a member of the public can reach with a browser and no credentials — the company's own website, developer portal and documentation, the specifications it publishes for public use (OpenAPI, AsyncAPI, JSON Schema, apis.json, llms.txt and similar), its public repositories, and its public status, pricing and changelog pages. Nothing here is obtained by breaching a system, defeating an access control, or using credentials of any kind.

The rating is an independent assessment. The Kin Score and Agent Readiness rating are independently calculated scores of a company's public API artifacts, produced by API Evangelist against a published rubric. They are not certifications, endorsements, security assessments, or audits, and they score published artifacts — not the quality, safety, or security of the software.

Corrections, re-scores, and removal are free. No partnership, contract, or purchase is required, and you do not need to justify the request.

  • Something wrong? Open an issue on this repository, or email info@apievangelist.com.
  • Published something new? Ask for a re-score and we will re-run the rating.
  • Want the listing taken down? Say so and we will honor it. The profile is reduced to your company name, a factual description, and a link to your own site, and the company is recorded as unrated — never scored zero for having asked.

Response times. Acknowledgement within one business day; removal or restriction within two business days; corrections and re-scores within five business days.

On a security or compliance team? Email info@apievangelist.com with 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 so your team can see the same surface we did, and we will take the listing down on request while you work through it.

Full detail: Where this data comes from

2C2P is a Singapore-headquartered payments platform serving merchants across Southeast Asia and beyond. Its Payment Gateway (PGW) API - currently Payment v4.3 - lets merchants accept cards, e-wallets, QR, installments, and alternative payment methods through a server-to-server REST interface. 2C2P is part of Ant International.

Access Model (Read This First)

  • Merchant onboarding, not self-serve keys. Production access requires a 2C2P merchant account (commercial onboarding / KYC). 2C2P issues a Merchant ID and a Secret Key from the merchant profile - there is no public "get an API key" button in the docs.
  • JWT-signed requests. The PGW API does not use an Authorization header. Every request body is a JSON Web Token (JWS) whose payload carries the transaction fields and whose signature authenticates the merchant. The merchant signs the JWT with its Secret Key using HMAC SHA-256 (HS256); 2C2P returns a JWT signed the same way, which the merchant verifies and decodes. The merchant is identified by the merchantID inside the signed payload. Select endpoints also support a JWT+JWS (asymmetric) variant.
  • Sandbox then production. Build and test against the sandbox, then switch hosts for production:
    • Sandbox: https://sandbox-pgw.2c2p.com/payment/4.3
    • Production: https://pgw.2c2p.com/payment/4.3
  • Async results are webhooks, not sockets. Payment outcomes are delivered as a backend notification: 2C2P POSTs a signed JWT to the merchant's backendReturnUrl, and the browser is redirected to frontendReturnUrl. There is no WebSocket or SSE API.
  • PCI-reducing card capture. With Secure Fields, card input elements are loaded from 2C2P directly into the merchant's checkout page, returning an encryptedCardInfo / securePayToken that is submitted inside the signed Do Payment request - raw PAN never touches the merchant server.

APIs.json: https://raw.githubusercontent.com/api-evangelist/2c2p/refs/heads/main/apis.yml

Tags

  • Payments
  • Payment Gateway
  • Southeast Asia
  • Singapore
  • Thailand
  • Cards
  • E-Wallet
  • Payment Token
  • Cross-Border
  • Fintech

Timestamps

  • Created: 2026-07-12
  • Modified: 2026-07-12

APIs

All PGW v4.3 operations are HTTPS POST with JWT (JWS) request/response bodies. Base URL: https://pgw.2c2p.com/payment/4.3 (production) or https://sandbox-pgw.2c2p.com/payment/4.3 (sandbox).

2C2P Payment Token API

Server-to-server POST that initializes a payment and returns a paymentToken plus a webPaymentUrl for the hosted payment page. Carries invoiceNo, amount, currencyCode, description, and channel / tokenize options.

2C2P Do Payment API

Executes a payment against a paymentToken, selecting the channel (card, e-wallet, QR, installment, pay-later, loyalty) via the payment code and supplying card, customer, browser, and return-URL data. Supports the direct / Secure Fields integration.

2C2P Payment Option API

Returns the payment options and channel details available for a given paymentToken - methods, groupings, and per-channel metadata used to render a custom checkout (paymentOption, paymentOptionDetails).

2C2P Payment Inquiry API

Retrieves the full result of a transaction by merchantID and invoiceNo (or paymentToken via transactionStatus), returning amount, status, approval and reference codes, masked account / card token, installment, and FX details.

2C2P Payment Maintenance API

Post-authorization maintenance - void / cancel a transaction via cancelTransaction, plus refund and settle operations covered by the payment maintenance guides.

2C2P Card Token & Recurring API

Card tokenization and stored-credential operations - cardTokenInfo for saved card tokens and cardInstallmentPlanInfo for installment plans - together with the recurring payment plans used for subscriptions and returning buyers.

2C2P Exchange Rate API

Retrieves currency exchange rates for a transaction, supporting dynamic currency conversion (DCC) and alternative-payment-method MCC exchange rates. A JWT+JWS secured variant is available.

2C2P Secure Fields

Browser-side card capture that loads 2C2P-hosted input elements into the merchant's own checkout page, returning an encryptedCardInfo / securePayToken that is passed to the Do Payment (or SecurePay) API so raw PAN never touches the merchant server. Reduces merchant PCI scope.

Artifacts

Real vs. Modeled

  • Confirmed: the base hosts (pgw.2c2p.com, sandbox-pgw.2c2p.com), the Payment v4.3 endpoint paths, the JWT (JWS) HMAC SHA-256 auth model, and the Merchant ID + Secret Key credential flow are all documented on developer.2c2p.com.
  • Modeled: the request/response field schemas in the OpenAPI and collections are a representative subset derived from the documented parameters, presented as decoded JSON for readability. Verify exact payloads against the 2C2P developer portal. Per-transaction pricing is not publicly published and is not reconciled.

Common Properties

Maintainers

FN: Kin Lane Email: kin@apievangelist.com

About

2C2P is a Singapore-headquartered payments platform serving merchants across Southeast Asia and beyond. Its Payment Gateway (PGW) API - currently Payment v4.3 - lets merchants accept cards, e-wallets, QR, installments, and alternative payment methods via a server-to-server REST interface where every request and response body is a JWT (JWS) signed…

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors