generated: '2026-08-27' method: searched source: https://docs.silverflow.com/guides/sandbox name: Silverflow sandbox docs: - https://docs.silverflow.com/guides/sandbox - https://docs.silverflow.com/guides/getting-started environments: - name: Sandbox (Europe) base_url: https://eu-west-1.api-sbx.silverflow.com/v1 alias: https://api-sbx.silverflow.co/v1 declared_in: openapi/silverflow-openapi.yml servers[] - name: Production (Europe) base_url: https://eu-west-1.api.silverflow.com/v1 alias: https://api.silverflow.co/v1 - name: Production (North America) base_url: https://us-east-2.api.silverflow.com/v1 access: self_serve: false note: >- There is no public self-service sign-up. Sandbox access is provisioned through Silverflow onboarding — an Agent Activation Token is issued, POST /v1/agents/{agentKey}/activate mints the first API key, and further keys are created with POST /v1/apiKeys. A technical account manager (TAM) is assigned. This is a gated sandbox, not an open playground. activation_operation: activateAgent key_creation_operation: createApiKey credentials: model: >- Same credential model as production — API key `key` + `secret` used as HTTP Basic, or an agent bearer JWT. There is no test-vs-live key prefix; keys are prefixed `apk-` in both environments and separation is by environment host, not by key prefix. key_prefix: apk- agent_prefix: cgt- fidelity: connects_to_card_networks: false note: >- "Silverflow's sandbox environment does not connect to the card networks' simulators. Card network and issuer responses are generated by Silverflow internal components, intended to mock production responses." The sandbox validates connectivity and request/response integration; it is explicitly NOT an exhaustive model of network or issuer behaviour, and Silverflow directs complex business-logic validation to the assigned TAM. test_data: pan_policy: >- PANs are not strictly validated in sandbox. Any PAN of 12-19 digits whose prefix falls in the ranges below is accepted and routed to that network. pan_prefixes: - prefix: '4' network: visa - prefix: 34, 37 network: american-express - prefix: 36, 39 network: diners - prefix: 51-55, 22-27 network: mastercard - prefix: 56-58 network: maestro - prefix: 60, 64, 65 network: discover - prefix: 420035, 541353 network: bancontact threeds_pans: - pan_prefix: '46354400000022' length: 16 network: visa method_url: https://eu-west-1.sit-sbx.silverflow.com/v1/acs/method-initiate - pan_prefix: '341111' length: 15 network: american-express method_url: https://eu-west-1.sit-sbx.silverflow.com/v1/acs/method-initiate - pan_prefix: '55203300000022' length: 16 network: mastercard method_url: https://eu-west-1.sit-sbx.silverflow.com/v1/acs/method-initiate - pan_prefix: 420035, 541353 length: 16 network: bancontact triggers: model: >- Sandbox behaviour is amount-driven. The transaction amount (in minor units) is structured as SCENARIO + TEST CASE (2 digits) + RESPONSE CODE (3 digits) — e.g. amount 100005 triggers network response code 05 (Do not honor). For POS the two-digit test case is dropped because amounts above 5000 would force a PIN prompt, so only scenario + response code are used. Only the scenarios published in the guide are supported. threeds: - scenario: Frictionless flow trigger: amount.value < 3000 - scenario: Challenge flow trigger: amount.value > 3000 OR challengeIndicator = challenge-preferred - scenario: Un-authenticated flow trigger: card.holderName = fake - scenario: Silverflow returns HTTP 500 trigger: card.holderName = error authorization: see errors/silverflow-decline-codes.yml (decline_codes[]) — the amount->response-code matrix is captured there in full avs: - amount: 414000 avs_result: 'N' - amount: 418000 avs_result: R - amount: 421000 avs_result: U - amount: 423000 avs_result: W - amount: 424000 avs_result: X - amount: 425000 avs_result: 'Y' - amount: 426000 avs_result: Z cvc: - amount: 513000 cvc_result: M - amount: 514000 cvc_result: 'N' - amount: 514147 cvc_result: 'N' response_code: N7 (Visa) - amount: 514005 cvc_result: 'N' response_code: 05 (Mastercard) - amount: 514100 cvc_result: 'N' response_code: 100 (Amex) - amount: 516000 cvc_result: P - amount: 519000 cvc_result: S - amount: 521000 cvc_result: U - amount: 522000 cvc_result: 'Y' - amount: 530006 cvc_result: '006' network: diners - amount: 530007 cvc_result: '007' network: diners atm_cash_withdrawal: - amount: 80000 description: Refer to card issuer mastercard_response_code: '01' - amount: 82000 description: Pick-up card mastercard_response_code: '04' - amount: 84000 description: Stolen card mastercard_response_code: '43' - amount: 86000 description: Not sufficient funds mastercard_response_code: '51' - amount: 88000 description: Expired card mastercard_response_code: '54' - amount: 90000 description: Incorrect PIN mastercard_response_code: '55' - amount: 92000 description: Exceeds withdrawal limit mastercard_response_code: '61' - amount: 94000 description: PIN tries exceeded mastercard_response_code: '75' account_name_inquiry: - amount: 610000 result: Full Match visa: '00' mastercard: '00' - amount: 620000 result: Partial Match visa: '00' mastercard: '00' - amount: 630005 result: No Match visa: '05' mastercard: '05' - amount: 640000 result: Name Validation Not Performed visa: '00' - amount: 650000 result: Name Validation Not Supported visa: '00' mastercard: '00' - amount: 660000 result: Invalid Issuer Response visa: '00' reversal: - scenario: Reversal (ISO 0400) behaviour: always approved (response code 00) - scenario: Reversal advice (ISO 0420) behaviour: always approved (00; 400 on Amex/Diners) time_simulation: test_clocks: false note: >- Silverflow publishes no test clock / time-travel facility. Time-dependent behaviour (clearing windows, `clearAfter`, dispute deadlines) is not documented as simulatable in sandbox. fixture_tooling: published: false note: No CLI, fixture generator or scenario-trigger endpoint is published; scenarios are triggered purely by request values (amount, holderName, PAN prefix). no_fabrication_note: >- Every PAN prefix, amount trigger, holder-name trigger and response code above is copied verbatim from Silverflow's published sandbox guide. No test value here was invented.