Overview
Use payment connections, merchant accounts, routing profiles, routing rules, provider routing decisions, payment intents, attempts, requests, responses, and health records.
Problem
Payment execution needs a governed provider-selection and observability layer.
Solution
Model provider connectivity and routing in PayStream, then retain request, response, attempt, decision, and health records around each payment operation.
How it works
Configure provider and merchant records, define routing profiles and rules, create payment intents, record attempts and provider decisions, and track provider requests, responses, status mappings, and health checks.
Who is this for
Payments Administrator
Finance Operations
Expected outcomes
- Consistent provider-selection state
- Provider request and health observability around payment operations
Key metrics
Security impact
- Payment connections, merchant accounts, routing rules, payment intents/attempts, provider requests/responses, status mappings, and health records · PII: yes where billing, customer, payment, bank, invoice, or external reference data identifies a person or organization
Compliance
- Workspace permissions, trusted execution, resource authorization, Core secrets, finance audit, and app-scoped grants.
Availability & next steps
Team
Business
Enterprise