Web Services (SOAP)

The Thredd Web Services provide a flexible way to interface to Thredd to create and manage the cards in your programme. Card enrolment in services such as 3D Secure and tokenisation are also managed using web services.

The Thredd web service is based on SOAP Version 1.1. SOAP (Simple Object Access Protocol), which is a messaging protocol for exchanging structured information in the implementation of web services. It uses Extensible Markup Language (XML) for its message format and relies on application layer protocols such as HTTP for message negotiation and transmission. SOAP allows developers to invoke processes running on disparate operating systems (such as Windows, macOS, and Linux) to authenticate, authorise and communicate using XML.

Figure: Web Services API Architecture - using SOAP

Below are examples of how Thredd Web Services can be used:

• Create, activate and load cards

• Manage card PINs, cards status and other features of a card

• Apply dynamic card controls

• View and manage the balance on the card

• Apply card fees

• Enroll and manage cards in the 3D Secure service

• Enroll and manage cards in the Tokenisation service (Visa (VDEP) and Mastercard (MDES) Tokenisation service)

For more details, refer to the Web Services Guide.