Payment Authorization
Keep payment authorization connected to the booking, invoice, customer, and configured payment processor.
Use the Processor for Authorization
The payment provider handles the authorization decision. Booking Ninjas keeps that result connected to the operational record.
Authorization Request
Send the payment request through the configured processor.
Processor Response
Receive the approved, declined, or other status returned by the processor.
Connected Record
Keep the authorization result tied to the related booking, invoice, or customer record.
Payment Follow-Up
Use the returned status in the next billing or payment step.
Keep Authorization Status Visible
Make it easier for staff to see what happened without checking a separate payment system first.
Approved
Keep approved payment activity tied to the related billing record.
Declined
Show the declined status returned by the payment provider.
Pending or Review
Keep other processor statuses visible where the integration supports them.
History
Keep payment and authorization activity available for later review.
Authorization Depends on the Payment Provider
Card checks, bank-payment rules, fraud controls, and supported payment methods come from the processor and integration used.
Cards
Card authorization follows the rules and response provided by the configured processor.
Bank Payments
Bank-transfer or ACH support depends on the payment provider and implementation.
Fraud Controls
Fraud screening and risk controls are provided by the payment processor or related payment service.
New Providers
A payment provider not already supported may require a separate integration scope.
Works With the Payment Flow
Authorization is one step in the wider payment and billing workflow.
Payment Processing
Use the configured processor to handle the transaction and return its status.
View Payment Processing →Online Payment Collection
Let customers pay invoices, deposits, and balances through the supported payment flow.
View Online Payment Collection →Payment Reconciliation
Match recorded payment activity back to the related billing records.
View Payment Reconciliation →Pricing
Payment authorization works through Core billing and the configured payment processor.
Core Package
Starts with 1–50 Active Bookable Units.
- Booking Engine + Reservation System
- Invoicing and Billing
- Recurring Billing
- Standard reports and dashboards
- Supported built-in integrations where relevant
Payment Processor
Provider pricingAuthorization, transaction, card, bank-payment, and gateway costs depend on the payment provider used.
- Processor and transaction fees are separate
- Authorization behavior depends on the provider
- Fraud controls depend on the provider
- New integrations may require separate scope
Separate Authorization Tool vs Booking Ninjas
Keep the processor response connected to the booking and billing workflow instead of tracking it separately.
| Capability | Manual Tracking | Booking Ninjas | Standalone Payment Tool |
|---|---|---|---|
| Authorization decision | Outside the workflow | Returned by configured processor | Handled by payment tool |
| Booking context | Manual lookup | Connected to operations | Needs integration |
| Invoice context | Manual update | Same billing workflow | Needs integration |
| Payment status | Manual tracking | Connected record | Payment-system record |
| Fraud controls | Depends on method | Depends on processor | Depends on provider |
| Provider fees | Depends on method | Separate provider cost | Separate provider cost |
Frequently Asked Questions
Keep Authorization Connected to the Payment
Use the processor for authorization and keep the result connected to bookings, invoices, and customer records.