Worldline · Authentication Profile

Wordline Authentication

Authentication

Worldline secures its APIs with http and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

PaymentsPayment ProcessingAcquiringIssuingOpen BankingDigital BankingFinTechEurope
Methods: http, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in:

Security Schemes

basic oauth2
· flows: clientCredentials
Authorization http
scheme: bearer

Source

Authentication Profile

wordline-authentication.yml Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/worldline-card-issuing-api-2.41.1.json, openapi/worldline-open-banking-payment-initiation-3.15.0.yaml
summary:
  types:
  - http
  - oauth2
  oauth2_flows:
  - clientCredentials
schemes:
- name: basic
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://sbx-wlip.api1-eu2.psapigateway.preprod.giservices.io/token
    scopes: 0
  sources:
  - openapi/worldline-card-issuing-api-2.41.1.json
- name: Authorization
  type: http
  scheme: bearer
  description: |-
    The 'Authorization' field must be filled with an access token.
    #### How to get an access token
    To request an access token, the Initiating Party must digitally sign the relevant request headers using the private key that corresponds to the certificate uploaded to the Open Banking Service Portal. This action is to be performed in the `POST /token` endpoint.

    Upon a successful request, the Open Banki
  sources:
  - openapi/worldline-open-banking-payment-initiation-3.15.0.yaml