GPI APIs enable financial institutions to retrieve transaction information and update payments in real time. To learn more about this API, see the GPI API overview. In this section, you will find the technical implementation details on how to integrate with GPI APIs.
Refer to the OpenAPI specifications and detailed specifications, which complement the OpenAPI specifications, to help you integrate the API.
| GPI Payment Market Infrastructure API Reference | Detailed Specification |
| Universal Confirmations API Reference | Detailed Specification |
| Transaction Details API Reference | Detailed Specification |
Understanding the business rules is necessary when integrating with GPI APIs. These rules are explained in the following rulebooks in the Swift Knowledge Centre.
Looking for a faster and easier way to integrate? Consider using one of the developer tools designed to simplify the consumption of API-based services available on the Swift platform. Build your application with Swift SDK to help you with lower-level application plumbing, which includes authentication, authorisation, signing and error handling. Alternatively, consider using Swift Microgateway to configure, monitor all API calls you make on Swift and capture inbound API requests. Finally, Swift zero-footprint is an option that provides reference implementations so that you can create your own SDK or utilities.
Not sure which tool is right for you? Try the connectivity option selector to get recommendations from our expert. After you select a tool, try setting it up in the API sandbox (available over the Internet) to quickly get started.
The GPI API sandbox returns static sample responses and does not contain any application logic. This sandbox is recommended for developers who want to learn and understand the authentication method JWT Bearer Grant Type by testing it out with a self-signed certificate over the Internet. This sandbox also ensures that the application generates valid requests and can consume valid responses conforming to OpenAPI specifications. It is also recommended for developers who are trying to set up the developer tools aimed to make integration easier.
You can view, fork or download the Postman collection which includes authentication API calls and sample GPI APIs calls. Also refer to access sandbox where dedicated sandbox credentials are provided. To start testing in the sandbox, create an app and select gpi API.
| GPI APIs | Postman Collections |
|---|---|
| GPI Customer Credit Transfer API Postman Collection | |
| GPI Customer Cover Payment API Postman Collection | |
| GPI Financial Institution Transfer API Postman Collection | |
| GPI Payment Market Infrastructure API Postman Collection |
The Swift Pilot environment closely resembles the Live environment. It is intended to fully qualify your API integration. Make sure you are subscribed to GPI Customer Credit Transfer (gCCT) service. Follow the steps below to access the Swift Go API Pilot testing environment.
Create a dedicated app for testing in the Pilot environment and select gpi API from the list of API products. Inside the app are consumer-key and consumer-secret which are the application credentials used to identify the application calling the API. After creating the app, promote the app to the Pilot environment.
GPI APIs support the use of Business certificates and Channel certificates when signing the JWT in the authorisation API call. After creating the certificate, assign the RBAC role swift.apitracker!p to the certificate.
This step should be completed by a security officerClick to learn more about SWIFTNet PKI Security Officer registration in the Knowledge Centre..
After completing the steps above, you now have the credentials required to access the GPI APIs in the Pilot environment. Refer to Authentication to learn how to use the credentials you created above to start testing your integration with this API in Pilot.
After successfully testing the GPI APIs in Pilot, follow the steps below to start using this API in Live.
Promote the app you created to the Live environment or create a new app for the Live environment. If you decided to create a new app, select gpi API from the list of API products. After creating the app, promote the app to the Live environment.
You should promote the app to Pilot first and then Live.
Follow the same process for creating the certificate for Pilot testing. GPI APIs supports the use of Business certificates and Channel certificates when signing the JWT in the authorisation API call. After creating the certificate, assign the RBAC role swift.apitracker to the certificate for Live.
This step should be completed by a security officerClick to learn more about SWIFTNet PKI Security Officer registration in the Knowledge Centre..
Swap out the credentials you used for Pilot with Live credentials and start using the GPI APIs in your Live applications. When in doubt, refer to Authentication to learn how to use your Live credentials to access this API in Live.
| Universal Confirmations API Postman Collection |
| Transaction Details API Postman Collection |