Operational Responsibilities
SenteRail handles the platform side of enabled payment workflows. Your team still owns the application, support, fulfilment, and reconciliation decisions inside your own system.
Customer-Owned Controls
| Control | Your responsibility |
|---|---|
| Credentials | Store keys safely and rotate them when needed |
| Idempotency | Use stable keys for mutating requests and retries |
| Webhooks | Verify signatures, dedupe events, and persist before processing |
| Fulfilment | Release goods, services, or member updates only after verified state |
| Reconciliation | Match SenteRail events with your own records |
| Support | Keep references and evidence for customer questions |
Launch Operations
Before launch, assign owners for credentials, webhook delivery, reconciliation, support, and legal/commercial escalation. A production launch should not depend on one developer remembering how the integration works.
Incident Handling
When an incident happens, do not guess state from a single signal. Compare API responses, signed webhook events, your own records, and support evidence. If the mismatch affects customers, hold fulfilment or member-facing action until the state is resolved.