About this Guide
This guide provides information on the stages in a typicalThredd card project.
Target Audience
Technical team(s) responsible for setting up a new card program.
What's Changed?
If you want to find out what's changed since the previous release, see the Document History section.
How to use this Guide
-
To find out about the stages in a typical Thredd card setup project, see Stages in a Project.
-
To understand about how Thredd manages changes once your program is up and running, see Managing Change.
Related Documents
Refer to the table below for a list of other relevant documents that should be used together with this guide.
Document |
Description |
---|---|
Describes the card payments ecosystem and how Thredd supports your card program. |
|
Describes how to use the Thredd SOAP API to send requests to Thredd and provides specifications on the available web service calls. |
|
Describes how to use the Thredd REST API to send requests to Thredd . It includes generic Getting Started information as well as reference details for each of the endpoints. |
|
Describes theThredd External Host Interface (EHI) and provides specifications on how to process and respond to messages received from EHI. |
|
Describes the structure and contents of the Thredd Transaction XML reports. |
|
Describes how to use the Thredd Portal to manage your cards and transactions. |
|
Describes the Thredd 3D Secure (Apata) service and how to implement a 3D Secure project. |
For the latest technical documentation, see the Documentation Portal.