Skip to content

Merchant dashboard

Sandbox

Developer center

Phase 1 preview — all figures below come from placeholder data.

Mode

Sandbox routes every request to testnets and accepts only `sk_test_` keys.

SandboxNo mainnet funds can move.

Signature verification

HMAC-SHA256, timestamped and replay-protected within 5 minutes.

Gatesettle-Signature: t=…,v1=…

API keys

Keys are hashed at rest — the full secret exists only at creation time. Scope every key and allow-list the caller IPs.

3 API keys
LabelPrefixScopesModeIP allow-listLast used
Production — storefrontsk_live_9Qa2…readwritelive203.0.113.10
Sandbox — CIsk_test_4Rb7…readwritetestany
Payout automationsk_live_1Zc5…readpayoutlive203.0.113.24, 203.0.113.25

Webhook endpoints

Secrets are rotatable with a dual-secret overlap window. An endpoint failing for three days is disabled automatically and the owners are notified.

2 webhook endpoints
EndpointEventsSecretStatus
https://shop.example.com/hooks/gatesettle4 subscribedwhsec_••••••••••••7f3ahealthy
https://ops.example.com/hooks/payouts3 subscribedwhsec_••••••••••••b21c2 failures

Ordering is not guaranteed

The event `id` is the idempotency key; reconcile against `created` and the object state rather than delivery order.

Webhook logs

Retries back off 1m → 5m → 30m → 2h → 6h → 24h. Every attempt is replayable.

4 recent deliveries
EventAttemptResponseLatencyDelivered
payment_intent.settled1200184 ms
payment_intent.confirmed1200142 ms
payout.failed35003021 ms
payout.created2timeout—