CreatePaymentIntent
RiskcommandConnectors / Payments
Payment connector operations
Provider-neutral payment contracts, signed webhook evidence, approval-bound money movement, and reference setup for Adyen.
Canonical commands
5
intent, auth, capture, void, refund
Provider
Adyen
adyen
Webhook topics
2
required signed events
Receipts
3
command, webhook, operation
Canonical contract
Payment providers plug into the same command chain and evidence model. Provider-specific fields remain extensions on the connector package.
AuthorizePayment
RiskcommandCapturePayment
RiskcommandVoidPayment
RiskcommandRefundPayment
Riskapproval-boundAdyen reference connector
adyen / payments.adyen / v0.1.0
Reference payment connector surface. Runtime connector manifests live in the connectors repo and are read through platform contracts after split.
Evidenceadyen.payment-events
Payment events
Webhook topics and alerts
Provider events stay declared in the connector manifest so health, replay, and alert surfaces inspect the same contract.
AUTHORISATION
RequiredProvider authorisation result.
CAPTURE
RequiredProvider capture result.
Config surface
Connector-specific settings are extension keys, while payment operations stay on the shared payment command contract.