Architecture

Overview

Syllecta Cloud exposes two public surfaces:

• Idempotency API – /v1/record stores payment or order state with automatic deduplication.
• Webhook Gateway – /v1/webhooks/:provider receives provider notifications, validates them, and forwards normalized payloads to your backend.

Everything else (queueing, retries, storage, usage tracking) is handled inside Syllecta so you can focus on your business logic.

High-Level Diagram

Client Application ──> Syllecta Cloud (Idempotency API) ──> Client Backend

Webhook Provider ──> Syllecta Cloud (Dedupe & Forward) ──> Client Backend

Core Behaviors

• Idempotent REST writes – Use POST /v1/record to check/lock and PUT /v1/record to persist the result; retries reuse the cached record.
• Tenant-aware authentication – API keys map each call to a tenant, plan, and usage limits without any extra plumbing.
• Webhook verification – Stripe, Shopify, PayPal/Braintree, GitHub, and generic HMAC payloads are validated before Syllecta forwards them to you.
• Automatic retries – Webhook deliveries are retried with exponential backoff until they succeed or exhaust the tenant’s policy.

What You Control

• Configure API keys and webhook secrets in Backoffice.
• Decide which fields to persist in /v1/record bodies.
• Provide a callback URL where Syllecta should POST normalized webhook payloads.

Everything else (signature checking, dedupe, queueing, dashboards) is managed by Syllecta Cloud.