Skip to main content
Webhook validation is crucial for ensuring the security and authenticity of incoming webhook events from Rise B2B API.

Webhook Security Overview

Webhooks provide real-time notifications but must be validated to ensure they come from Rise and haven’t been tampered with. Our webhook validation uses HMAC-SHA256 signatures for security.

Signature Verification

  • HMAC-SHA256 signatures
  • Timestamp validation
  • Replay attack prevention
  • Tamper detection

Security Benefits

  • Authentic source verification
  • Data integrity assurance
  • Attack prevention
  • Compliance requirements

Webhook Signature Format

Rise sends webhooks with a signature header in this format:
Where:
  • t = Unix timestamp
  • v1 = HMAC-SHA256 signature

Using the Webhook Validator

Basic Validation

Safe Validation (Returns Result)

Manual Validation

Parse Signature Header

Validate Timestamp

Compare Signatures

Complete Validation Example

Error Handling

Common Validation Errors

Logging and Monitoring

Security Best Practices

Environment Configuration

Validation Configuration

Security Checklist

1

Secret Management

Store webhook secret securely Use environment variables Never commit secret to version control Rotate secrets regularly
2

Validation

Validate all incoming webhooks Check timestamp tolerance Verify signature format Handle validation errors
3

Monitoring

Log validation failures Monitor webhook activity Set up alerts for suspicious activity Track validation metrics
4

Error Handling

Return appropriate HTTP status codes Log detailed error information Implement retry logic for failures Monitor error rates

Testing Webhook Validation

Test with Sample Data

Unit Tests

Next Steps

  1. Security Overview - Complete security architecture
  2. Secondary Wallets - Using dedicated wallets
  3. Best Practices - Security best practices