Supported with Core

Payment Processing

Connect payments to bookings, invoices, balances, and customer records through a supported payment processor.

Payment processing

Connect the Payment to the Operation

Keep payment activity tied to the booking, invoice, customer, or billing record that created it.

icon

One-Time Payments

Process a one-time payment through the configured provider.

icon

Deposits

Collect deposits where the booking or billing workflow requires them.

icon

Recurring Charges

Use recurring billing for repeat payment schedules where configured.

icon

Invoice Balance

Keep the payment and remaining balance connected to the invoice.

Follow the Payment Status

Use the response from the payment provider in the billing workflow.

Authorization

Keep the authorization result returned by the configured processor.

Payment Status

Keep approved, declined, pending, or other supported statuses visible.

Refunds

Handle refund activity through the configured payment and refund workflow.

History

Keep recorded payment activity available for later review and reporting.

Payment Methods Depend on the Provider

Available cards, bank payments, wallets, fraud controls, and transaction rules depend on the processor and integration used.

Cards

Card support and transaction behavior follow the configured payment processor.

Bank Payments

ACH or other bank-payment support depends on the provider and implementation.

Processor Fees

Processor, gateway, and transaction fees are separate from the Booking Ninjas subscription.

New Providers

A provider not already supported may require a separate integration scope.

Works With the Billing Flow

Payment Processing sits between authorization, collection, reconciliation, and refunds.

Payment Authorization

Keep the processor's authorization result connected to the payment record.

View Payment Authorization →

Online Payment Collection

Let customers pay invoices, deposits, and balances online.

View Online Payment Collection →

Payment Reconciliation

Review payment records against related invoices and billing activity.

View Payment Reconciliation →

Refund Management

Keep refunds tied to the original payment and billing record.

View Refund Management →

Pricing

Booking Ninjas connects the billing workflow to a supported payment processor.

Separate provider costs

Payment Processor

Provider pricing

Payment methods, authorization, transaction pricing, settlement, and gateway costs depend on the provider used.

  • Processor and transaction fees are separate
  • Payment methods depend on the provider
  • Provider fraud controls remain provider-managed
  • New integrations may require separate scope
Implementation depends on the payment provider, payment flow, billing rules, data, integrations, testing, and rollout. Learn why →

Standalone Processor vs Booking Ninjas

The processor handles the transaction. Booking Ninjas keeps it connected to the wider booking and billing workflow.

Capability Manual Tracking Booking Ninjas Standalone Processor
Transaction processingHandled separatelyThrough configured processorCore function
Booking contextManual lookupConnected to operationsNeeds integration
Invoice contextManual updateSame billing workflowNeeds integration
Recurring billingManual scheduleIncluded in CoreDepends on provider/product
Refund contextManual trackingConnected billing recordProcessor record
Processor feesDepends on methodSeparate provider costProvider pricing

Frequently Asked Questions

Does Booking Ninjas process the transaction itself?

The transaction is handled through the configured payment processor. Booking Ninjas connects the payment result to the related operational and billing records.

Which payment methods are supported?

Available cards, bank payments, wallets, and other methods depend on the processor and integration used.

Are payment processor fees included in Core?

No. Processor, gateway, and transaction fees are separate from the Booking Ninjas subscription.

Can Booking Ninjas support recurring payments?

Recurring billing is included in Core. The payment method and processor behavior depend on the provider and implementation.

What if we use a processor that is not already supported?

The integration can be reviewed separately. A new reusable connector may be treated as Product Expansion, while a client-specific integration may require Dedicated Customization.

Keep Payments Connected to the Booking

Use a supported processor while keeping payment status connected to invoices, balances, bookings, and customer records.

WhatsApp Us

WhatsApp Us