Log Streams
How Log Streams works in Paycux, what it is for, and the smallest setup that gets it running.
Understanding Log Streams
Understanding Log Streams is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
IP allowlist
IP allowlist is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Admin Portal
Admin Portal is a hosted set of screens your customers use to configure their own connection. You generate a signed link, they finish the setup, and you stay out of the email thread.
Links are single-purpose and expire. Generate one per task — SSO setup, directory setup, domain verification — rather than one link for everything.
Streaming Destinations and Payload Formats
Streaming Destinations and Payload Formats is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Datadog
Datadog is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Splunk
Splunk is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
AWS S3
AWS S3 is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.
Google Cloud Storage
Google Cloud Storage is handled by Log Streams rather than by your application code. Paycux exposes it through the same API surface as the rest of the platform, so the client you already configured needs no additional setup.
Configuration lives in the dashboard and is versioned per environment. Change it in staging, confirm the behaviour, then apply the same change to production.