For a service-based booking website, the Cybersource REST API is usually the best starting point. Since you're processing one-time payments for cleaning services rather than managing a product catalog, you can keep the integration relatively straightforward.
A common approach is:
• Customer submits a booking request.
• Create the booking in your system.
• Collect either a deposit or full payment through Cybersource.
• Use the transaction response to update the booking status automatically.
Regarding your questions:
• For one-time service payments, the Payments API is typically sufficient.
• Decision Manager is optional. For smaller service businesses with moderate transaction volume, many start without it and add fraud management later if needed.
• The REST API is flexible enough to support custom booking workflows, including quote requests, deposits, balance payments, and booking confirmations.
• For deposits, store the booking first and process only the required amount. The remaining balance can be charged later through a separate transaction.
• For payment confirmations, use Cybersource webhooks or server-side transaction validation rather than relying solely on the client-side response.
One recommendation is to keep payment processing separate from the booking form logic. This makes it easier to manage failed payments, refunds, booking updates, and future automation.
We've implemented similar API-based workflows for service businesses, and keeping bookings, payments, and notifications as separate processes generally results in a more reliable integration.
