Developer

Launch checklist

Less than 5 minutes to read

These are the recommended steps to take before launching your Sage Banking Service integration into production and live to customers. While they might not all be required for the minimal operation of your solution, these steps will help make your integration more robust, secure, efficient, and maintainable.

You can use the checkboxes to keep track of your progress.

Production ready

Complete the test plan for each of your banks.

If you have not done so already, request production credentials.

Ensure you're using your production client ID and secret.

Update the Provider API sandbox base endpoint URL to production.

Update the Sage ID sandbox endpoint URL to production.

Ensure you're correctly caching your JWT tokens, in accordance with JWT best practices

Onboarding

Store the bank account identifier for the onboarded customer.

When a bank account 'resource created' notification is recieved, send the first set of transactions.

Posting transactions

Only send transactions equal to and greater than the start date specified by the customer.

You should only be sending a maximum of 1,000 transactions for a single bank account at any given time.

Make sure your solution checks that the first set of posted statements has a status of 'succeeded' before attempting to post the next set.

Make sure you are handling the duplicate transaction error.

Securing your solution

Check that the Authorisation ID recieved through the authorisation notification matches an identifier sent through the query parameters to your GET /auth endpoint.

If you are verifying the Sage ID Authorisation header, make sure you're using the production JSON web key set.

If you have provided a custom headerName and headerValue to be sent with the /notification request to your solution, ensure this is being verified.

Add access token validation to ensure requests can be trusted.

Allow Cloudflare IP addresses on the connector API for additional security.

Go Live

Complete production testing, you can use our test plan for guidance.

Beta test your Banking Service solution with some initial customers.

Support process

We want to provide the best experience for our mutual customers choosing to use the Banking Service. As users are connecting through a Sage product, our support team will often be first to identify issues. A clear support proccess must be created to allow us to submit issues to you for escalation.

Outline your customer support process and service-level agreements.

Arrange an incident management solution for Sage to log issues.

What’s next?

After you have completed sandbox testing, you are ready to move into production. Find out how to upgrade to beta with Stage 4. Go live and support.