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
Worldline

Worldline Dispute API

Dispute Api Controller

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Dispute. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 13 operations across 13 paths, and defines 42 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.

13 operations 13 paths 42 schemas 3 GET10 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 Dispute API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (basic) using the clientCredentials flow.

Paths & Operations 13

Across 13 paths, the API surfaces 13 operations — 3 GET, 10 POST. Each is listed below with its method, path, parameters, and response codes.

Dispute 13

Dispute Api Controller

POST
/issuers/{issuerId}/operations/{externalOperationReference}/disputesdeprecated
Create Dispute
createDispute 6 params body → 400401403404500502200
GET
/issuers/{issuerId}/disputes/{disputeFolderReference}
Get the dispute information of the folder
getDisputeFolderInformation 7 params → 400401403404500502200
GET
/issuers/{issuerId}/operations/{externalOperationReference}/disputedeprecated
Get the dispute information of the operation identified by external operation reference
getDisputeFolderInfoByExternalOperationReference 7 params → 400401403404500502200
GET
/issuers/{issuerId}/disputes/external-disputes/{issuerDisputeExternalReference}
Get the dispute information of the folder identified by external reference
getDisputeFolderInfoByIssDisputeExtRef 7 params → 400401403404500502200
POST
/issuers/{issuerId}/disputes/{disputeFolderReference}/postings
Perform a posting (Refund or WriteOff) related to the Dispute Folder
createPosting 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/external-disputes/{issuerDisputeExternalReference}/postings
Perform a posting related to the Dispute Folder by external reference
createPostingByIssDisputeExtRef 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/{disputeFolderReference}/events
Create an Event in the Dispute Folder
createEvent 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/external-disputes/{issuerDisputeExternalReference}/events
Create an Event in the Dispute Folder by external reference
createEventByIssDisputeExtRef 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/{disputeFolderReference}/documents
Add an External Document to the Dispute Folder
createDocument 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/external-disputes/{issuerDisputeExternalReference}/documents
Add an External Document to the Dispute Folder by external reference
createDocumentByIssDisputeExtRef 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/{disputeFolderReference}/generate-chargeback
Generate a ChargeBack to the scheme by dispute reference
generateChargeback 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/disputes/external-disputes/{issuerDisputeExternalReference}/generate-chargeback
Generate a ChargeBack to the scheme by external reference
generateChargebackByIssDisputeExtRef 6 params body → 400401403404500502200
POST
/issuers/{issuerId}/super-folders
create a super folder (beta)
createSuperFolder 5 params body → 400401403404500502200

Schemas 42

The contract defines 42 schemas that model the data the API accepts and returns. The most detailed are Dispute (33 properties), CreateDisputeRequest (10 properties), DisputeMessage (8 properties), DisputePosting (7 properties). Each schema is shown below with its type and property counts.

InternalServerErrorResponseMetadata
object
4 properties 4 required
ApiResponseEntityCreateDocumentResponse
object
Issuer response entity
2 properties 1 required
ResponseMetadata
object
6 properties 4 required
DisputeFolderIdentifier
object
2 properties 1 required
BadRequestErrorApiResponse
object
1 property 1 required
ApiResponseEntityGenerateChargebackResponse
object
Issuer response entity
2 properties 1 required
NotFoundErrorApiResponse
object
1 property 1 required
ForbiddenErrorApiResponse
object
1 property 1 required
NotFoundResponseMetadata
object
4 properties 4 required
CreateDocumentRequest
object
5 properties 3 required
UnauthorizedErrorApiResponse
object
1 property 1 required
Dispute
object
33 properties
GenerateChargebackResponse
object
2 properties
Links
object
2 properties 1 required
CardIdentifier
object
Identification of the card either by Issuer card external reference or by card reference
2 properties
CreateSuperFolderResponse
object
2 properties 1 required
CreateDisputeResponse
object
5 properties 1 required
ForbiddenResponseMetadata
object
4 properties 4 required
CreatePostingRequest
object
4 properties 2 required
CreateEventRequest
object
2 properties 1 required
CreateDisputeRequest
object
10 properties
ApiResponseEntityCreatePostingResponse
object
Issuer response entity
2 properties 1 required
InternalServerErrorErrorApiResponse
object
1 property 1 required
UnauthorizedResponseMetadata
object
4 properties 4 required
ApiResponseEntityCreateEventResponse
object
Issuer response entity
2 properties 1 required
SuperFolderIdentifier
object
1 property
DisputeMessage
object
8 properties
BadGatewayErrorApiResponse
object
1 property 1 required
CreateSuperFolderRequest
object
2 properties 1 required
BadRequestResponseMetadata
object
4 properties 4 required
ApiResponseCreateSuperFolderResponse
object
Create Superfolder Response entity
2 properties 1 required
GenerateChargebackRequest
object
6 properties 1 required
CreateEventResponse
object
2 properties 2 required
CreateDocumentResponse
object
3 properties 2 required
DisputePosting
object
7 properties
CreatePostingResponse
object
3 properties 3 required
BadGatewayResponseMetadata
object
4 properties 4 required
ApiResponseEntityCreateDisputeResponse
object
Issuer response entity
2 properties 1 required
Amount
object
3 properties 3 required
ApiResponseEntityDispute
object
Issuer response entity
2 properties 1 required
DisputeEvent
object
4 properties
DisputeDocument
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wordline-dispute-api-openapi.yml Raw ↑

Other APIs Worldline publishes across the network.

Worldline Connect (Global Collect) API
AE Profile APIs.io
Worldline Direct (Global Online Pay) API
AE Profile APIs.io
Worldline Acquiring API
AE Profile APIs.io
Worldline Financial Services Issuing API
AE Profile APIs.io
Worldline Financial Services Acquiring API
AE Profile APIs.io
Worldline Open Banking API
AE Profile APIs.io
Worldline SmartPOS API
AE Profile APIs.io
Worldline Identity and Authentication API
AE Profile APIs.io
Worldline Account - AccountState API
AE Profile APIs.io
Worldline Account API
AE Profile APIs.io
Worldline Account - Authorization API
AE Profile APIs.io
Worldline Account - Authorization Restriction API
AE Profile APIs.io
#Dispute
← Back to W APIs
API Details
ID
wordline:wordline-dispute-api
Base URL
https://api.connect.worldline-solutions.com
Docs
https://docs.connect.worldline-solutions.com/
Provider
Worldline
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=wordline-dispute-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/wordline-dispute-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 Worldline Dispute 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.