Payment Providers

Payment Provider (PSP) apps integrate Hantera's payment system — and in particular the Payment actor — with external Payment Service Providers. Each PSP app:

• Translates Payment actor lifecycle events (authorize, capture, refund, void) into the provider's protocol
• Handles incoming webhooks from the provider and applies the corresponding commands to the Payment actor
• Exposes provider-specific configuration (API credentials, environments) via app settings

Many PSP apps also ship with a Commerce integration — ingresses, hooks, and a storefront flow — so the cart-to-payment-to-order pipeline works end-to-end without additional integration work. Commerce integration is a convenience, not a requirement: the Payment actor integration is the core of every PSP app.

If you're building your own PSP app, start with the generic Commerce PSP Integration guide. It documents the standard pattern shared by all PSP integrations.

Available PSP Apps

Kustom

Integrates the Payment actor with Kustom and ships with a complete Commerce cart integration. Kustom is an iframe-based checkout where the provider owns the entire checkout UI — address collection, shipping options, and payment method selection all happen inside an iframe rendered by Kustom.

Key features:

• Payment actor integration (authorize via checkout flow, capture, acknowledgement)
• Idempotent checkout ingress with iframe htmlSnippet (Commerce)
• Confirmation ingress and push-webhook fallback that both create the Payment, complete the cart, and acknowledge to Kustom (Commerce)
• Hash-based cart synchronization driven by OnCartMutation (Commerce)
• Capture flow via the OnPaymentCapture rule hook
• OnKustomValidation custom hook — let merchant rules veto checkout completion with a structured error returned to Kustom