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

PPRO Payment Sessions API

The Payment Sessions API from PPRO — 3 operation(s) for payment sessions.

PPRO Payment Sessions 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 Sessions. The published artifact set on APIs.io includes an OpenAPI specification and an API reference.

This API exposes 4 operations across 3 paths, and defines 74 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.eu.ppro.com.

4 operations 3 paths 74 schemas 1 GET1 PATCH2 POST

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 Sessions 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 3 paths, the API surfaces 4 operations — 1 GET, 1 PATCH, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Payment Sessions 4
POST
/v1/payment-sessions
Create payment session
createSession 1 param body → 200400
POST
/v1/payment-sessions/{session-id}/authorizations
Authorize payment charge or agreement
authorizeSession 1 param body → 200400
GET
/v1/payment-sessions/{session-id}
Get payment session
fetchSession 1 param → 200400
PATCH
/v1/payment-sessions/{session-id}
Update payment session
patchSession 2 params body → 200400

Schemas 74

The contract defines 74 schemas that model the data the API accepts and returns. The most detailed are TravelDetails (18 properties), AgreementAuthorizationResponse (17 properties), CreationRequest (17 properties), CreationResponse (13 properties). Each schema is shown below with its type and property counts.

AdditionalData
object
2 properties
AuthenticationMethod
object
1 property 1 required
PaymentObjectDetails
object
3 properties 2 required
RedirectAuthenticationSettingsDetails
object
1 property
ExternalThreeDs
object
11 properties
PaymentMethod
object
2 properties
RedirectAuthenticationDetails
object
2 properties
CreationRequest
object
17 properties 3 required
MultiFactorAuthenticationSettingsDetails
object
1 property
FetchResponse
object
10 properties
AirlineIndustryData
1 required
Challenge
object
4 properties
ProcessingFailure
object
6 properties
TravelDetails
object
18 properties
AirlineDetails
object
8 properties
AppIntentAuthenticationMethod
VaultedCardInstrument
1 required
RedirectAuthenticationSettings
ScanCodeAuthenticationSettings
AuthenticationSettings
object
1 property 1 required
InitialPaymentChargeResponse
object
3 properties
AppNotificationAuthenticationSettings
ScanCodeAuthenticationDetails
object
6 properties
InitialPaymentChargeForUpdate
object
6 properties
RedirectAuthenticationMethod
AuthorizationRequest
object
11 properties 1 required
ExternalThreeDsAuthenticationSettings
Client
object
2 properties
MoneyWithType
object
3 properties 2 required
MultiFactorAuthenticationSettings
Frequency
object
2 properties 1 required
Consumer
object
11 properties
EducationDetails
object
6 properties
ExceptionResponseBody
object
4 properties
AirlineTripSegment
object
7 properties
ScanCodeAuthenticationMethod
ThreeDsAuthenticationMethod
PaymentChargeDetails
2 required
PatchRequest
object
5 properties
ChargeAuthorizationResponse
object
11 properties
ThreeDsAuthenticationSettings
ThreeDsAuthenticationSettingsDetails
object
2 properties
Profile
object
6 properties
AgreementAuthorizationResponse
object
17 properties
ScanCodeAuthenticationSettingsDetails
object
1 property
Address
object
8 properties
ThreeDsAuthenticationDetails
object
2 properties
InitialPaymentCharge
object
7 properties 1 required
CardNetworkTokenDetails
object
7 properties
MultiFactorAuthenticationMethod
AppNotificationAuthenticationSettingsDetails
object
1 property
MockInstrument
PaymentAgreementDetails
2 required
PassthroughWallet
object
5 properties
IndustryData
object
1 property 1 required
AppNotificationAuthenticationMethod
PaymentInstrument
object
1 property 1 required
CardNetworkTokenInstrument
1 required
AppIntentAuthenticationDetails
object
1 property
BancontactAccountInstrument
1 required
VaultedCardDetails
object
8 properties 6 required
TravelIndustryData
1 required
OrderItem
object
6 properties 3 required
BancontactAccount
object
5 properties
Order
object
7 properties
ConsumerWithCountry
object
11 properties 1 required
CreationResponse
object
13 properties 1 required
BankAccountDetails
object
7 properties
AuthorizationResponse
object
5 properties
InstallmentPlan
object
2 properties 1 required
Money
object
2 properties 2 required
BankAccountInstrument
1 required
EducationIndustryData
1 required
PassthroughWalletInstrument
1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs PPRO publishes across the network.

PPRO Authorization Endpoints API
PPRO Capture Endpoints API
PPRO Dispute Reports API
PPRO Disputes API
PPRO Enrollment Endpoints API
PPRO Internal API
PPRO Merchants API
PPRO Payment Agreement Revocations API
PPRO Payment Agreements API
PPRO Payment Charge Controller API
PPRO Payment Charges API
PPRO Payment Instruments API
Where this information came from

This is an independent, third-party profile of PPRO Payment Sessions 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.