Purpose
1.2. Reduce manual intervention by automating payment status checks, receipt issuance, and subsequent service triggers post-payment.
Trigger Conditions
2.2. Customer receives invoice link via email/SMS and initiates payment online.
2.3. Payment gateway reports successful transaction via webhook or API callback.
2.4. Payment completion triggers workflow: update status, send receipt, initiate scheduling/follow-up.
Platform Variants
3.1. Stripe
• Feature/Setting: “PaymentIntent API” for card and wallet processing. Configure webhook for “payment_intent.succeeded.”
3.2. PayPal
• Feature/Setting: “Orders API” for payments; use “Webhooks” for PAYMENT.CAPTURE.COMPLETED.
3.3. Square
• Feature/Setting: “CreatePayment” in Payments API; listen to “payment.updated” webhook.
3.4. Authorize.Net
• Feature/Setting: “Accept Hosted” form; “Silent Post URL” for payment notifications.
3.5. Braintree
• Feature/Setting: “Transaction.sale()” function; handle “WebhookNotification.Kind.SubscriptionChargedSuccessfully.”
3.6. Razorpay
• Feature/Setting: “Orders API” to create orders; “payment.captured” webhook for post-payment automation.
3.7. Adyen
• Feature/Setting: “/payments” endpoint; configure HMAC-verified notification endpoint for “AUTHORISATION.”
3.8. Mollie
• Feature/Setting: “Create Payment API” call; webhook on “payment.paid.”
3.9. Worldpay
• Feature/Setting: “Orders API” for payment requests; webhook relay for status change.
3.10. 2Checkout (now Verifone)
• Feature/Setting: “Payment API Initiate” call, INS (Instant Notification Service) endpoint.
3.11. Klarna
• Feature/Setting: “Orders API” for purchase; “notification_url” parameter for status updates.
3.12. GoCardless
• Feature/Setting: “Create Payment API” for Direct Debit; webhook on “payment_confirmed.”
3.13. WePay
• Feature/Setting: “/checkout” endpoint creation; “Event API” for “checkout_status=completed.”
3.14. BlueSnap
• Feature/Setting: “Create Transaction API”; “Notification” URL for PATCH on payment.
3.15. Checkout.com
• Feature/Setting: “Payments API” POST call; “webhooks/payments” for status.
3.16. Sage Pay (Opayo)
• Feature/Setting: “Server Integration Payment” with “Notification URL.”
3.17. Amazon Pay
• Feature/Setting: “Create Charge Permission API”; “ChargePermissionNotification” endpoint.
3.18. Alipay
• Feature/Setting: “API Direct Payment Interface”; return_url for notification.
3.19. Flutterwave
• Feature/Setting: “Payment API v3” charge endpoint, webhook for payment events.
3.20. PayU
• Feature/Setting: “API Initiate Transaction”; Payment response URL/webhook for transaction finalization.
(Additional platforms may be similarly implemented using their payment initiation APIs and webhook/event notification features.)
Benefits
4.2. Improves customer experience via fast, convenient payment options.
4.3. Automates administrative follow-up and service scheduling steps.
4.4. Reduces payment errors and missed transactions through event-based automation.
4.5. Centralizes payment data for simplified reporting and tracking.