generated: '2026-07-24'
method: searched
source: https://cardsapidocs.thredd.com/docs/accessing-the-api
docs:
  accessing: https://cardsapidocs.thredd.com/v2.0/docs/accessing-the-api
  production_setup: https://cardsapidocs.thredd.com/v2.0/docs/integration-steps-set-up-on-production-environment
  card_test_service: https://cardsapidocs.thredd.com/v2.0/docs/card-test-service-cts
environments:
  - name: UAT (test)
    base_url: https://cardsapi-uat-pub.globalprocessing.net/
    api_base: https://cardsapi-uat-pub.globalprocessing.net/api/v1
    token_url: https://oauthuat.globalprocessing.net/connect/token
    purpose: Test and develop against the Cards API before going live.
  - name: Production
    api_base: https://api.thredd.com/api/v1
    purpose: Live issuing and processing (access via onboarding + go-live checklist).
credentials:
  provisioning: >-
    Test-environment credentials (client_id + client_secret) are generated by
    your Thredd Implementation Manager / Thredd Representative; they are unique
    to the environment being accessed. Thredd does not self-serve sandbox card
    numbers publicly.
  self_serve_note: >-
    The Developer Portal (devportal.thredd.com) grants a sandbox client id and
    secret for evaluating the API Hub.
test_tooling:
  - name: Card Transaction System (CTS) / Card Test Service
    description: >-
      Thredd's transaction simulation tooling used to generate and test card
      transactions (authorisations, presentments, loads, balances) against a
      test card in the UAT environment.
    docs: https://cardsapidocs.thredd.com/v2.0/docs/card-test-service-cts
onboarding_checklist: https://cardsapidocs.thredd.com/v2.0/docs/onboarding-checklist
note: No public magic test card numbers are published; test values are issued per programme.