How can I add a secure payment option to a service-based transportation website?

[firstmedtransit]

I’m working on a service-based transportation website where customers can request and schedule non-emergency transportation services. I’m considering adding an online payment option and want to understand the best approach for integrating a payment gateway into this type of workflow.

The website mainly handles service requests rather than traditional e-commerce products. I’d like to know:

1. Which Cybersource API would be suitable for one-time service payments?
2. Is it better to process payment after a service request is confirmed?
3. What is the recommended way to handle payment status callbacks or webhooks?
4. Are there any specific security considerations for a service-booking website?

I’d appreciate advice from developers who have implemented payment workflows for service-based websites.

[robercarter12]

For a service-based booking site, I’d usually confirm the request first and then process the payment, with webhooks used to keep the booking status synchronized. Security, idempotency, and verifying webhook signatures are especially important. The same booking-and-payment flow can also work well for gaming services or platforms.

[williamremero36]

A service-booking workflow makes sense here because payment timing can depend on when the transportation request is actually confirmed. I’d keep the payment processing on the server side, use Cybersource’s supported payment APIs rather than handling card data directly, and rely on verified webhook notifications to update the booking status. Tokenization or hosted payment fields can also reduce the amount of sensitive payment data your application handles.