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
PPRO

PPRO Payment Instruments API

The Payment Instruments API from PPRO — 2 operation(s) for payment instruments.

Documentation Provider Profile APIs.io OpenAPI GitHub

PPRO Payment Instruments API is one of 18 APIs that PPRO publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Payment Instruments. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 4 operations across 2 paths, and defines 34 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against 2 base URLs: https://api.sandbox.eu.ppro.com, https://api.ppro.com.

4 operations 2 paths 34 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.eu.ppro.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

PPRO Payment Instruments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearer_token). By default, every request must be authenticated.

Paths & Operations 4

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

Payment Instruments 4
GET
/v1/payment-instruments/{instrument-id}
Retrieve a Payment Instrument
fetchPaymentInstrument 2 params → 200
PUT
/v1/payment-instruments/{instrument-id}
Update an existing Payment Instrument
updatePaymentInstrument 2 params body → 200
DELETE
/v1/payment-instruments/{instrument-id}
Delete a Payment Instrument
deletePaymentInstrument 2 params → 204
POST
/v1/payment-instruments
Create a Payment Instrument
createPaymentInstrument 1 param body → 200

Schemas 34

The contract defines 34 schemas that model the data the API accepts and returns. The most detailed are BankAccountDetails (9 properties), VaultedCardDetails (8 properties), CardNetworkTokenDetails (7 properties), BancontactAccountDetails (7 properties). Each schema is shown below with its type and property counts.

CardNetworkTokenInstrumentRequest
1 required
VaultedCardInstrumentResponse
PassthroughWalletInstrumentRequest
UpiAutoPayInstrumentRequest
TwintWalletInstrumentRequest
BancontactAccountDetails
object
7 properties 5 required
BancontactAccountInstrumentRequest
BancontactAccountInstrumentResponse
AmazonPayInstrumentRequest
PassthroughWalletInstrumentResponse
CardNetworkTokenInstrumentResponse
PaymentInstrumentCreationRequest
object
1 property 1 required
UpiAutoPayDetails
object
1 property
KlarnaAccountDetails
object
2 properties
MockInstrumentResponse
BankAccountInstrumentRequest
KlarnaAccountInstrumentRequest
UpiAutoPayInstrumentResponse
PassthroughWalletDetails
object
5 properties
CardNetworkTokenDetails
object
7 properties 1 required
MockInstrumentRequest
KlarnaAccountInstrumentResponse
AmazonPayDetails
object
1 property
PaymentInstrumentResponse
object
3 properties 1 required
BankAccountInstrumentResponse
PaymentInstrumentRequest
object
1 property 1 required
VaultedCardDetails
object
8 properties
AmazonPayInstrumentResponse
BankAccountDetails
object
9 properties
TwintWalletInstrumentResponse
RawCardInstrumentRequest
2 required
PassthroughWalletInstrumentCreationRequest
InstrumentValidation
object
2 properties 1 required
RawCardDetails
object
The card details
6 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

ppro-payment-instruments-api-openapi.yml Raw ↑

Other APIs PPRO publishes across the network.

PPRO Authorization Endpoints API
AE Profile APIs.io
PPRO Capture Endpoints API
AE Profile APIs.io
PPRO Dispute Reports API
AE Profile APIs.io
PPRO Disputes API
AE Profile APIs.io
PPRO Enrollment Endpoints API
AE Profile APIs.io
PPRO Internal API
AE Profile APIs.io
PPRO Merchants API
AE Profile APIs.io
PPRO Payment Agreement Revocations API
AE Profile APIs.io
PPRO Payment Agreements API
AE Profile APIs.io
PPRO Payment Charge Controller API
AE Profile APIs.io
PPRO Payment Charges API
AE Profile APIs.io
PPRO Payment Sessions API
AE Profile APIs.io
#Payment Instruments
← Back to P APIs
API Details
ID
ppro:ppro-payment-instruments-api
Base URL
https://api.eu.ppro.com
Docs
https://developerhub.ppro.com/global-api/docs/welcome
Provider
PPRO
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=ppro-payment-instruments-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/ppro-payment-instruments-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 PPRO Payment Instruments 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.