Skip to content

Go-live checklist ​

Production is a separate environment with live data. Most of what it needs is set up by Salaxy, and your code mainly switches hosts and uses a production certificate. Work through this list in order; each item links to the topic that explains it. Examples use the test environment; see Environments for demo and production.

The way to productionFive steps from left to right. Build and test your integration in test or demo. Salaxy provisions the production accounts, channel and models. You switch the hosts and the certificate to production. You run a smoke test. Then you are live, with a customer care and escalation path in place.1Buildin test or demo2Provisionby Salaxy3Switchhosts andcertificate4Smoke testfirst run inproduction5Livecare andescalationPurple: Salaxy does it. Grey: you do it.
Production setup is mostly Salaxy's work; your part is the certificate, the host switch and the first run.

Before production ​

Tick each item. Items 1 to 5 are one-time setup; ask Salaxy for the production side early, because Salaxy does the provisioning.

#What must be trueWhoTopic
1Production partner account and technical account exist. They are separate from the test ones, with their own account idsSalaxy, with youPartner and technical accounts
2Production certificate is created and its private key is in your backend secret store. A test certificate fails in productionYouPartner and technical accounts
3Payment channel is provisioned in production and you have verified itSalaxy, with youPayment channels
4Service models are provisioned in production, and you have agreed which customers get which modelSalaxy, with youService models
5Accounting models are provisioned in production and linked from the service modelsSalaxyAccounting models
6Hosts are switched from test to production, see belowYouEnvironments
7Customer and accounting firm account creation works in productionYouCustomer accounts, Accounting firm accounts
8Smoke test passed, see belowYou, with Salaxythe topic pages you use
9Customer care and escalation path is named, see belowYou, with SalaxyDeveloper FAQ

The order of the topics you build is in Integration overview and Integration in a day with a coding agent. Items 1 to 5 are the same topics, with the production values: the test values are not reused.

Switch from test to production ​

Production is its own environment with its own data. Change these together, and keep the host settings in configuration, not in code.

WhatTestProduction
REST API basehttps://test-secure.salaxy.comhttps://secure.salaxy.com
Token endpointhttps://test-secure.salaxy.com/oauth2/tokenhttps://secure.salaxy.com/oauth2/token
Embed hosthttps://test-embed.palkkaus.fi/https://embed.palkkaus.fi/
CertificateTest certificateProduction certificate, signed by the production root
Account ids (including the channel's owner account), service and accounting model idsTest valuesProduction values from Salaxy
  • Do not reuse a test certificate or a test id in production. Production certificates are verified against a different root, and ids are different.
  • The payment channel key does not change. It is fixed in code and is the same in test and production; only its owner account differs. See Payment channels.
  • Demo does not exercise the production certificate path. Demo shares test data and uses the test root; only production proves the production certificate.
  • Switch API and embed hosts together if you use the embedded white label.
  • Authentication is unchanged: the same signed JWT flow, only the host, the certificate and the account ids differ. See REST authentication.

Smoke test ​

A suggested checklist, not a fixed Salaxy procedure. Run one complete case in production before real customers use it. Production sends real payments and real payslips, so use a case that is meant to be paid.

Customer care and escalation ​

Two flows are easy to confuse. Name a person for each before go-live.

FlowWho asksWho answers
End-customer care — a payroll question from a customer company or an accounting firmThe end customerUsually you first, and you escalate to Salaxy what you cannot resolve. Your partner contract sets the actual split, and Salaxy publishes no standard response-time commitment
Escalation to Salaxy — a developer or operator needs something from SalaxyYouSalaxy support

Reasons to escalate to Salaxy, during development and after go-live:

  • Missing test data or test accounts (Test endpoints and test data).
  • Provisioning: technical account, payment channel, service and accounting models.
  • Whether your payment channel has an outbound status trigger.
  • A manual monthly-cycle run in test, where the cycle does not run end to end (Monthly cycle).
  • A server-side log lookup: send the request id and an approximate time (Limits, logging and correlation).

Decide early whether Salaxy may be named to your end customers. In an embedded white label integration the customer sees your brand, so first-line staff need to know what they can say. Help channels are on Support.

Checklist ​

  • Items 1 to 9 above are ticked, with production values and no test certificate or test id left.
  • Hosts, certificate and ids come from configuration, one set per environment.
  • A smoke test, for example the one suggested above, has run through the whole loop your integration uses, in production.
  • You have a named person for end-customer care and a named Salaxy contact for escalation.
  • You log request ids and know how to quote them to Salaxy.

Every page is also available as Markdown: add .md to its URL — a folder page such as white-label/ is white-label/index.md. Index for LLMs: llms.txt. Questions: Support.