Go-Live Checklist

Request production launch only after every applicable item below is complete.

Portal and approval

• Partner and card programme information is complete and current.
• The intended card type, subtype and use case are approved.
• Template verification is complete and Testing Mode has been handled according to the launch procedure.
• Production identifiers, certificates and endpoints are configured; test values are not present in production configuration.

Implementation

• The production service generates the selected ATW link method correctly.
• The official entry-point asset and fallback behaviour are implemented on every supported channel.
• Card payloads satisfy the common and card-type-specific specifications.
• Callback and lifecycle endpoints authenticate requests, validate inputs and behave idempotently.
• Update, cancellation, expiry and deletion scenarios have been tested where applicable.

Security and operations

• Private keys and credentials are held in an approved secret store and are not present in source code, client applications or logs.
• Certificate expiry and rotation are monitored.
• Time synchronisation, request tracing, alerting, retry limits and incident ownership are in place.
• Partner support can trace a failed journey using the time, Card ID, refId and request ID without collecting unnecessary personal data.

Launch evidence

• End-to-end acceptance results are recorded for supported devices, regions and channels.
• Known limitations and user-facing fallbacks are documented.
• Technical and business owners have approved the launch scope.

For launch or integration issues, use Technical Support.