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

Worldline Mobile Payment Operations API

Apple Pay Controller

Worldline Mobile Payment Operations API is one of 79 APIs that Worldline publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Mobile Payment Operations. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 16 operations across 16 paths, and defines 53 schemas. It is described by OpenAPI 3.2.0, at version 2.41.1.

Requests are made against a single base URL, https://sbx-wlip.api1-eu2.psapigateway.preprod.giservices.io/card-issuing/api/v2.

16 operations 16 paths 53 schemas 4 GET12 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.41.1
Base URL
https://api.connect.worldline-solutions.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Worldline Mobile Payment Operations API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (basic) using the clientCredentials flow.

Paths & Operations 16

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

Mobile Payment Operations 16

Apple Pay Controller

POST
/issuers/{issuerId}/cards/{cardReference}/create-apple-tokenized-card
Token Provisioning: Apple push provisioning
createAppleTokenizedCard 5 params body → 200400403404500
POST
/issuers/{issuerId}/cards/{cardReference}/create-vts-tokenized-card
Token Provisioning: Google or Samsung push provisioning (Visa variant)
createVtsTokenizedCard 5 params body → 200400403404500
POST
/issuers/{issuerId}/cards/{cardReference}/create-mdes-tokenized-card
Token Provisioning: Google or Samsung push provisioning (Mastercard variant)
createMdesTokenizedCard 5 params body → 200400403404500
POST
/issuers/{issuerId}/tokens/{tokenReference}/generate-crypto-otp
Token Provisioning: Get-Crypto-OTP by Token
getCryptoOTPByToken 5 params body → 200400403404500
POST
/issuers/{issuerId}/cards/{cardReference}/generate-crypto-otp
Token Provisioning: Get-Crypto-OTP by card reference
getCryptoOTPByCardReference 5 params body → 200400403404500
GET
/issuers/{issuerId}/cards/{cardReference}/token-list
Selfcare : Get Token list from a Card Reference
getTokenData_1 4 params → 200400403404500
GET
/issuers/{issuerId}/tokens/{tokenReference}/tokenRequestors/{tokenRequestorId}/details
Selfcare : Get token details
getTokenDetails 6 params → 200400403404409410500
POST
/issuers/{issuerId}/tokens/{tokenReference}/update
Selfcare : Update a token status
updateToken 5 params body → 202400403404409500
GET
/issuers/{issuerId}/tokens/{tokenReference}/card-reference
Selfcare : Get Card Reference From Token
getCardIdFromToken_1 5 params → 200400403404409500
POST
/issuers/{issuerId}/cards/{cardReference}/click-to-pay-enroll
Click-To-Pay: Enroll a card
clickToPayEnroll 5 params body → 202400403404422500
POST
/issuers/{issuerId}/cards/{cardReference}/click-to-pay-remove
Click-To-Pay: Remove a card or complete account
clickToPayRemove 6 params → 202400403404422500
GET
/issuers/{issuerId}/cards/{cardReference}/click-to-pay-account-data
Click-To-Pay: Return all data provisioned for a given card
retrieveAccountData 5 params → 200400403404422500
POST
/issuers/{issuerId}/cardholders/{cardholderReference}/update
Update click-to-pay cardholder data
clickToPayUpdate 6 params body → 202400403500
POST
/issuers/{issuerId}/vts-apple-push-datadeprecated
Issuer service aimed to generate data specific elements for push provisioning with ApplePay (MBPAD, MBPAC)
vtsApplePushDataUsingPOST 2 params body → 200400401403404500502
POST
/issuers/{issuerId}/vts-mobile-banking-auth-codedeprecated
Issuer service aimed to generate data specific elements for app to app provisioning (MBAAC)
vtsPushProvisioningRequestUsingPOST 2 params body → 200400401403404500502
POST
/issuers/{issuerId}/vts-payment-instrument-detailsdeprecated
Issuer service aimed to generate data specific elements for push provisioning for VTS
vtsPushProvisioningRequestUsingPOST_1 2 params body → 200400401403404500502

Schemas 53

The contract defines 53 schemas that model the data the API accepts and returns. The most detailed are AddTokenData (14 properties), VtsPaymentInstrumentsDetailsRequest (12 properties), ConsumerInformation (9 properties), DetailsDataResponse (9 properties). Each schema is shown below with its type and property counts.

InternalServerErrorResponseMetadata
object
4 properties 4 required
ResponseMetadata
object
6 properties 4 required
AddBaseRequest
object
1 property 1 required
ApiResponseEntityMobileBankingAppAuthCodeResponse
object
Issuer response entity
2 properties 1 required
CreateVtsTokenizedCardV2Response
object
1 property
BadRequestErrorApiResponse
object
1 property 1 required
NotFoundErrorApiResponse
object
1 property 1 required
ResponseV2
object
2 properties 1 required
ForbiddenErrorApiResponse
object
1 property 1 required
NotFoundResponseMetadata
object
4 properties 4 required
EncryptedPayload
object
EncryptedPayload object containing a FundingAccountData object
5 properties 3 required
ClickToPayEnrollUpdateRequest
object
2 properties
UnauthorizedErrorApiResponse
object
1 property 1 required
GetCryptoOTPV2Response
object
1 property
FundingAccountInfo
object
Json structure containing encrypted payload
3 properties 1 required
MdesIssuerDigitizationDataResponse
object
The data that must be returned to the mobile application and transmitted to wallet provider
2 properties 1 required
ResponseV2GetCardIdFromTokenV2Response
object
2 properties 1 required
Links
object
2 properties 1 required
DetailsDataResponse
object
9 properties
ResponseV2ClickToPayRetrieveAccountDataResponse
object
2 properties 1 required
ResponseV2CreateMdesTokenizedCardV2Response
object
2 properties 1 required
CreateMdesTokenizedCardV2Request
object
1 property 1 required
ForbiddenResponseMetadata
object
4 properties 4 required
ResponseV2GetCryptoOTPV2Response
object
2 properties 1 required
CreateMdesTokenizedCardV2Response
object
1 property
ResponseV2CreateAppleTokenizedCardV2Response
object
2 properties 1 required
VtsPaymentInstrumentsDetailsRequest
object
12 properties
ApplePayPushProvisioningResponse
object
2 properties
ApiResponseEntityVtsPushProvisioningResponse
object
Issuer response entity
2 properties 1 required
ResponseV2CreateVtsTokenizedCardV2Response
object
2 properties 1 required
VtsMobileBankingAuthCode
object
2 properties
ClickToPayRetrieveAccountDataResponse
object
4 properties
InternalServerErrorErrorApiResponse
object
1 property 1 required
UnauthorizedResponseMetadata
object
4 properties 4 required
ConsumerInformation
object
Structure used for information related to click-to-pay account
9 properties 5 required
ResponseV2GetTokenDataV2Response
object
2 properties 1 required
GetCardIdFromTokenV2Response
object
5 properties
ApiResponseApplePayPushProvisioning
object
Issuer response entity
2 properties 1 required
AddTokenData
object
Structure used for filling information related to the found tokens. Present if minimum one token found
14 properties 3 required
VtsPushProvisioningResponse
object
1 property
BillingAddress
object
7 properties 4 required
BadGatewayErrorApiResponse
object
1 property 1 required
MobileBankingAppAuthCodeResponse
object
1 property
VtsCommonPushProvisioningRequest
object
5 properties 5 required
CreateAppleTokenizedCardV2Response
object
3 properties
BadRequestResponseMetadata
object
4 properties 4 required
ResponseV2DetailsDataResponse
object
2 properties 1 required
VtsApplePushDataRequest
object
4 properties
TokenSelfcareUpdateRequest
object
2 properties 2 required
CardDetails
object
List of cardDetail structures that contains information on cards associated to a click-to-Pay account. Returned if min one present. See below for subfields
8 properties 5 required
BadGatewayResponseMetadata
object
4 properties 4 required
GetTokenDataV2Response
object
4 properties
CreateAppleTokenizedCardV2Request
object
6 properties 4 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wordline-mobile-payment-operations-api-openapi.yml Raw ↑

Other APIs Worldline publishes across the network.

Worldline Connect (Global Collect) API
Worldline Direct (Global Online Pay) API
Worldline Acquiring API
Worldline Financial Services Issuing API
Worldline Financial Services Acquiring API
Worldline Open Banking API
Worldline SmartPOS API
Worldline Identity and Authentication API
Worldline Account - AccountState API
Worldline Account API
Worldline Account - Authorization API
Worldline Account - Authorization Restriction API
Where this information came from

This is an independent, third-party profile of Worldline Mobile Payment Operations 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.