Settings
Solution model and connectivity mode are independent. Changing one never changes the other, and neither change ever sends a Cybersource API request.
Solution model
Persisted to browser local storage and application state. Determines whether a Cybersource transit token (transient token) is used in place of card data for deferred payments.
Deferred payments send tokenInformation.jti. A transit token is auto-created if missing.
Connectivity mode
Changing this never sends an API request. It only decides what happens the next time you trigger a payment operation.
Mock — all operations simulated, no network calls
Demonstration data
Re-seed the network and regenerate a full demo day (taps → journeys → aggregations). Existing taps, journeys, payments and cases are cleared.
Cybersource configuration (server-side)
Read from environment variables on the server. The shared secret and key id are never sent to the browser or returned by any API response — only the redacted status below.
Environmenttest
Base URLhttps://apitest.cybersource.com
Merchant IDjeremybus
Auth methodhttp_signature
Key IDb64c…b48c
Shared secretpresent (redacted)
Live calls enabledtrue
Sandbox readyyes
Mock vs Sandbox behaviour
Mock: no outbound network calls. Every Cybersource operation returns a documentation-shaped simulated response, labelled “Simulated”.
Cybersource Sandbox: when credentials are complete and CYBS_LIVE_CALLS_ENABLED=true, a real HTTP Signature-signed request is sent to https://apitest.cybersource.com. If anything is missing, or the call fails, the platform transparently falls back to a simulated response and records why.
Current: solution TOKENIZED, connectivity MOCK.