Skip to content

Configure for production ΒΆ

Once production validation is done, the transit provider can be added to the production Benefits database.

Most of these steps are typically performed by a Cal-ITP developer.

  1. Transit agency creates a customer group for production use in production Littlepay.
  2. Transit agency associates the group with the discount product created previously during production validation.
    • Once this is complete, Cal-ITP verifies that the setup is correct by using the littlepay CLI.
  3. Cal-ITP creates a TransitAgency in the prod environment
  4. Cal-ITP creates a new LittlepayGroup in the Benefits prod environment:
    • Associate the new LittlepayGroup with the correct transit provider and enrollment flow using the dropdowns.
    • Set the ‘Group id’ to the corresponding production group ID (from production Littlepay).

  5. Cal-ITP creates a new LittlepayConfig in the Benefits prod environment:

    • Set Environment to Production.
    • Return to the TransitAgency and associate the new LittlepayConfig as its ‘Transit processor config’.- Choose the new TransitAgency.
    • Retrieve Audience and Client ID values for the production config from shared LastPass note.
    • Client Secret Name: ${agency_slug}-payment-processor-client-secret
    • Create the corresponding secret in the Azure Key Vault for the environment
    • Be sure to refresh the secrets for this to take effect!
      1. In the Azure portal, go to the App Service.
      2. Inside the App Service, navigate to Settings -> Environment variables.
      3. Click the Pull reference values button to force the App Service to bypass the 24-hour cache and fetch the latest values for Key Vault references. This triggers a graceful restart of the app.

  6. Cal-ITP returns to the TransitAgency instance and checks the Active box.

  1. Cal-ITP creates a TransitAgency in the prod environment

  2. Cal-ITP creates a new SwitchioConfig in the Benefits production environment:

    • Environment: Production
    • Label: ${agency_short_name}
    • Tokenization api key: from LastPass
    • Tokenization api secret name: ${agency_slug}-switchio-prod-api-secret
    • Create the corresponding secret in the Azure Key Vault for the environment
    • Be sure to refresh the secrets for this to take effect!
      1. In the Azure portal, go to the App Service.
      2. Inside the App Service, navigate to Settings -> Environment variables.
      3. Click the Pull reference values button to force the App Service to bypass the 24-hour cache and fetch the latest values for Key Vault references. This triggers a graceful restart of the app.
    • Enrollment api authorization header: See LastPass (same for all agencies in the env)
    • Pto id: from LastPass
    • Client certificate: Switchio (prod) client certificate (same for all agencies in the env)
    • Ca certificate: Switchio (prod) CA certificate (same for all agencies in the env)
    • Private key: Switchio (prod) private key (same for all agencies in the env)

  3. Cal-ITP creates a new SwitchioGroup in the Benefits prod environment for each enrollment flow:

    • Associate the new SwitchioGroup with the correct transit provider and enrollment flow using the dropdowns.
    • Unlike Littlepay, Switchio group IDs are consistent across environments and agencies, so that does not need to be set here.
  4. Cal-ITP returns to the TransitAgency instance and selects the SwitchioConfig above as the agency’s transit processor config and checks the Active box.

At this point, real customers can begin enrolling their cards and receiving their discounted fares with this transit provider!

Next steps: