Get started
Less than to read
The Transaction Import Connector is a Sage Provider API (PAPI) connector which has a range of features which are intended for the scenario when a customer’s bank account doesn’t have a provider feed of account information directly available to Banking Service. The purpose of the Transaction Import Connector, is to provide the ability for customers to manually import bank transactions.
Use Cases
- A customer’s bank account doesn’t have a provider feed of transactions available directly from the bank and they’re waiting for a feed to become available.
- A customer wanting to ‘top up’ transactions which are not available directly from the bank.
Access Token
The Transaction Import Connector is a Sage Provider API (PAPI) connector which means that a JWT may be generated using the accessToken api endpoint (with requires a signature generated using the standard authorisation method). This JWT can then be provided as a Bearer token in the Authorisation header: ‘Bearer ‘.
Sage has assembled a Postman Collection to illustrate the Transaction Import Connector API methods and workflow. The Postman Collection includes the functionality to POST an organisation, and request a JWT.
Setting up and making requests
Sage has assembled a Postman Collection to illustrate the Sage Banking Service Provider API methods and workflow.
Read the Provider API Postman Collection guide.
Transaction Import statuses
Throughout the lifecycle of a Transaction Import, you’ll see various statuses when performing a GET request.
You can read more about the statuses and when you’ll see them here State Machine Statuses.