Production checklist

Credentials and environments

• Production credentials are stored in a server-side secret manager.
• Staging and production credentials are separate.
• System clocks are synchronized for the required X-Timestamp header.
• API keys, HMAC secrets, and signatures are excluded from logs.

Decision handling

• The payment flow branches only on should_block.
• should_block: true prevents settlement, including incomplete evaluations.
• Settlement does not wait for alerts, Mule analysis, or case creation.
• Unknown response fields do not break response parsing.

Reliability

• Connect and read timeouts are explicitly configured and load-tested.
• A timeout is recorded as an unknown outcome, not a failed evaluation.
• Concurrent submissions for one reference_id are prevented locally.
• The continuity policy for timeouts, 500, and 503 is approved.
• Reconciliation retains reference_id, trx_id, and the caller-generated X-Request-ID.

Data and account mapping

• Outbound and inbound account mappings have been tested.
• customer_id belongs to the evaluated bank-owned account.
• Optional personal data is minimized.
• account_snapshot.account_id matches evaluated_account_id when a snapshot is sent.

Operations

• Expected traffic and burst behavior have been reviewed with Vantrace.
• Monitoring records latency, HTTP status, evaluation status, and identifiers.
• Alerts exist for authentication failures, incomplete decisions, and dependency failures.
• The integration test cases pass in an authorized non-production environment.