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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
CyberSource

CyberSource Customer Payment Instrument API

A Customer Payment Instrument is linked to a Customer and an Instrument Identifier.It stores additional information in relation to a card number(PAN) or bank account (echeck).

Documentation Provider Profile APIs.io OpenAPI GitHub

CyberSource Customer Payment Instrument API is one of 84 APIs that CyberSource publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Customer Payment Instrument. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 5 operations across 2 paths. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, https://apitest.cybersource.com/.

5 operations 2 paths 0 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://api.cybersource.com
Resource Areas
1

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Customer Payment Instrument 5

A Customer Payment Instrument is linked to a Customer and an Instrument Identifier. It stores additional information in relation to a card number(PAN) or bank account (echeck).

POST
/tms/v2/customers/{customerId}/payment-instruments
Create a Customer Payment Instrument
postCustomerPaymentInstrument 2 params body → 201400403409424500
GET
/tms/v2/customers/{customerId}/payment-instruments
List Payment Instruments for a Customer
getCustomerPaymentInstrumentsList 4 params → 200400403404410424500
GET
/tms/v2/customers/{customerId}/payment-instruments/{paymentInstrumentId}
Retrieve a Customer Payment Instrument
getCustomerPaymentInstrument 3 params → 200400403404410424500
PATCH
/tms/v2/customers/{customerId}/payment-instruments/{paymentInstrumentId}
Update a Customer Payment Instrument
patchCustomersPaymentInstrument 4 params body → 200400403404410412424500
DELETE
/tms/v2/customers/{customerId}/payment-instruments/{paymentInstrumentId}
Delete a Customer Payment Instrument
deleteCustomerPaymentInstrument 3 params → 204400403404409410424500

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cybersource-customer-payment-instrument-api-openapi.yml Raw ↑

Other APIs CyberSource publishes across the network.

CyberSource Token Management Service (TMS) API
AE Profile APIs.io
CyberSource Decision Manager API
AE Profile APIs.io
CyberSource Recurring Billing API
AE Profile APIs.io
CyberSource Payouts API
AE Profile APIs.io
CyberSource Flex Microform API
AE Profile APIs.io
CyberSource Unified Checkout API
AE Profile APIs.io
CyberSource Payer Authentication (3D Secure) API
AE Profile APIs.io
CyberSource Reporting API
AE Profile APIs.io
CyberSource Transaction Search API
AE Profile APIs.io
CyberSource Webhooks API
AE Profile APIs.io
CyberSource Boarding API
AE Profile APIs.io
CyberSource Invoicing API
AE Profile APIs.io
#Customer Payment Instrument
← Back to C APIs
API Details
ID
cybersource:cybersource-customer-payment-instrument-api
Base URL
https://api.cybersource.com
Docs
https://developer.cybersource.com/docs/cybs/en-us/payments/developer/all/rest/payments.html
Provider
CyberSource
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cybersource-customer-payment-instrument-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cybersource-customer-payment-instrument-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of CyberSource Customer Payment Instrument API, 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.