Purpose
1.2. Reduce friction in the user experience by integrating checkout directly into the ticketing system, supporting multiple payment methods (credit/debit, mobile wallet, BNPL, etc.).
1.3. Ensure real-time ticket issuance and access control upon successful payment processing.
1.4. Automate reconciliation, refunds, and notifications without manual intervention.
1.5. Integrate fraud prevention, transaction tracking, and fulfil compliance requirements for digital transactions.
Trigger Conditions
2.2. System detects valid cart with tickets available for selected ride/time.
2.3. Payment initiation event is fired upon confirmation of intent to buy.
2.4. Payment gateway responds (success/failure/callback/webhook) and triggers ticket issuance or exception handling flow.
Platform Variants
• Feature/Setting: Payment Intents API – configure events for payment_success, payment_failed, and use the Checkout Session for seamless UI.
3.2. PayPal
• Feature/Setting: Orders v2 API – create and capture payment orders, with webhook for PAYMENT.CAPTURE.COMPLETED.
3.3. Square
• Feature/Setting: CreatePayment endpoint and Webhook for payment.updated – automate reconciliation and notifications.
3.4. Adyen
• Feature/Setting: Checkout API – Process payment, configure HMAC signature, enable notification webhooks.
3.5. Worldpay
• Feature/Setting: Hosted Payment Pages – set up redirect flows and callback URLs.
3.6. Authorize.Net
• Feature/Setting: Accept Hosted API – send accept.transaction webhook for outcome.
3.7. Razorpay
• Feature/Setting: Orders API – create payment link, subscribe to payment.webhook for result.
3.8. Braintree
• Feature/Setting: Transaction.sale API – configure return and webhook for transaction settlement.
3.9. Mollie
• Feature/Setting: Payments API – handle webhook payments, status change triggers.
3.10. 2Checkout (now Verifone)
• Feature/Setting: INS Webhooks – monitor payment processing and ticket delivery trigger.
3.11. Amazon Pay
• Feature/Setting: Pay API – integrate the Complete Checkout Session API, handle charge permission notifications.
3.12. Apple Pay
• Feature/Setting: Apple Pay JS API – embed JS for browser-driven flows, configure onpaymentauthorized event.
3.13. Google Pay
• Feature/Setting: Payment Request API – set up merchant profile and listen to payment authorized event.
3.14. Klarna
• Feature/Setting: Payments API – handle authorize/approve callbacks for instant checkout.
3.15. Alipay
• Feature/Setting: Cross-border Payment API – integrate alipay.acquire.create and async notification URLs.
3.16. WeChat Pay
• Feature/Setting: JSAPI Payment – configure wx.config and notify_url for real-time triggers.
3.17. BlueSnap
• Feature/Setting: Hosted Payment Fields – setup POST callbacks for payment processing events.
3.18. GoCardless
• Feature/Setting: Payments API – direct debit flow event triggers, webhook for payment_confirmed.
3.19. Ingenico ePayments
• Feature/Setting: Server API – configure Pay and Capture transactions, eq. to 3DSecure triggers.
3.20. PayU
• Feature/Setting: REST API – set up payment response handlers and notification callbacks.
Benefits
4.2. Reduce manual work for staff via automated confirmation, access control, and transaction reconciliation.
4.3. Real-time fraud monitoring, compliance fulfilment, and improved transaction analytics.
4.4. Enhanced user trust and convenience, growing conversion rates and customer satisfaction.
4.5. Support for refund, chargeback, and support ticket automation via end-to-end payment tracking.