Event-driven. Reliable. Ordered.
Every state change on the platform fires a structured webhook event with full idempotency keys and delivery guarantees. Build reactive systems without polling.
Every state change. Zero polling.
Stop writing polling loops. Techvica fires a structured JSON webhook for every meaningful event on the platform - ordered, signed, and guaranteed delivered at least once.
Delivery guarantees
- 01Structured JSON payloads for every event type
- 02Guaranteed at-least-once delivery
- 03Ordered event stream per resource
- 04Automatic retry with exponential backoff
- 05Webhook signing for payload verification
- 06Event replay for up to 30 days
Webhook payload structure
Event ID
Unique identifier for every event fired
Event type
Structured type like payment.completed or kyc.approved
Timestamp
ISO 8601 timestamp of when the event occurred
Idempotency key
Your original key echoed back for deduplication
Resource data
Full resource snapshot - amount, currency, rail, status
HMAC signature
SHA-256 signature for payload verification
Every event type, documented.
payment.created
Payment object initiated
payment.processing
Sent to payment rail
payment.completed
Funds settled
payment.failed
Rail rejected or timed out
kyc.approved
Identity verification passed
kyc.referred
Flagged for human review
fx.locked
FX rate locked for conversion
account.created
New account opened
Common questions about Webhooks
What events trigger webhooks on the Techvica platform?
Every meaningful state change fires a webhook: payment created, processing, completed, or failed; KYC approved or referred; FX rates locked; accounts created. The full event catalogue covers 30+ event types.
How does Techvica guarantee webhook delivery?
We guarantee at-least-once delivery with automatic retries using exponential backoff. If your endpoint is down, we retry for up to 72 hours. Every delivery attempt is logged.
Can I replay webhook events I missed?
Yes. Event replay is available for up to 30 days. You can replay individual events or all events within a time window via the API or dashboard.
How do I verify that a webhook is authentic?
Every webhook payload is signed with a SHA-256 HMAC using your webhook secret. You verify the signature header against the payload to confirm authenticity and prevent replay attacks.
Are webhook events delivered in order?
Events are ordered per resource. All events for a specific payment, account, or KYC check arrive in the order they occurred. Cross-resource ordering is not guaranteed.
What happens if my endpoint responds slowly?
We allow 30 seconds for your endpoint to respond with a 2xx status. Timeouts are treated as failures and retried. We recommend acknowledging quickly and processing asynchronously.
Build reactive systems on a reliable event stream.
Our engineers will walk you through the full event catalogue and help you design your webhook consumer architecture.
Follow the event-driven path
Developer APIs
Review the API and integration surface that pairs with Techvica webhooks.
Payments Engine
See which payment workflows generate the operational events your team needs to consume.
Analytics & Reporting
Connect live events with reporting and operational oversight across the platform.