42.1 Overview

The Currencies and Payment Configuration settings determine how prices are displayed and how customers pay for Products and Appointments through public VCards.

These settings control:

The customer dashboard provides account-level User Settings and a dedicated Payment Configuration section. The application saves general account settings and payment credentials through separate customer operations.

The programmed customer-payment workflow supports:

Not every configured gateway supports every currency, country, or checkout situation.

Understanding the Currency Structure

42.2 What a Currency Record Contains

A system currency normally includes:

Examples:

The Currency Code is particularly important because payment gateways use it when deciding whether a transaction can be processed.

42.3 Currency Name

The Currency Name describes the monetary unit.

Examples:

The name should correspond with the Currency Code and symbol.

42.4 Currency Code

The Currency Code is commonly a three-letter identifier.

Examples:

A payment gateway may reject a transaction even when the visible currency symbol appears correct if the underlying code is unsupported.

42.5 Currency Symbol

The symbol is displayed beside the monetary amount.

Examples:

A symbol alone may be ambiguous.

For example, $ can represent:

1. United States Dollar
2. Canadian Dollar
3. Australian Dollar
4. Other dollar-based currencies

Where customers may be uncertain, use the Currency Code in Product descriptions, checkout instructions, or policies.

42.6 Currency Does Not Perform Automatic Conversion

Changing a Currency does not automatically convert the numerical Price.

Example:

The system should not be assumed to calculate the current exchange rate or convert 100 USD into its equivalent EUR amount.

The user must enter the correct Price for the new Currency.

42.7 Currency Versus Payment Method

Currency answers:

What monetary unit is being charged?

Payment Method answers:

How will the customer pay?

Example:

A VCard may use one Currency while offering several compatible payment methods.

Account Currency Versus Product Currency

42.8 Account Default Currency

The account has a default Currency setting.

This Currency can be used when a Product or payment workflow does not have a more specific Currency assigned.

The public Product checkout retrieves the Product’s selected Currency when one exists. When it does not, the checkout can fall back to the VCard owner’s account Currency setting.

42.9 Product-Specific Currency

Each VCard Product can have its own Currency.

Example:

A Product-specific Currency allows the Product to display and process its Price independently of the account default.

42.10 Appointment Currency

Paid Appointment workflows rely on the account’s Currency and payment configuration.

Before activating paid Appointment booking:

1. Select the correct account Currency.
2. Set the Appointment or Service amount.
3. Configure a compatible Payment Method.
4. Test the public booking process.
5. Verify the Currency at the payment gateway.
6. Confirm the Appointment transaction.

42.11 Use One Primary Currency Where Possible

Using one primary Currency across the account can reduce:

1. Customer confusion
2. Incorrect Product prices
3. Unsupported gateway errors
4. Accounting complexity
5. Refund mistakes
6. Currency-label inconsistencies

Several currencies can be used when operationally necessary, but each Product and checkout should identify its Currency clearly.

42.12 Mixed-Currency Example

A VCard could contain:

This may be appropriate for a specialized international business, but it requires:

1. Accurate Prices
2. Compatible gateways
3. Clear customer communication
4. Separate accounting records
5. Currency-specific refunds
6. Careful testing

Opening Currency Settings

42.13 Opening User Settings

To review the account Currency:

1. Sign in to the customer dashboard.
2. Select Settings.
3. Open the General settings area.
4. Locate the Currency setting.
5. Select the intended Currency.
6. Review the display-format controls.
7. Select Save.
8. Test a public VCard.

The same User Settings area contains the dedicated Payment Configuration destination.

42.14 Selecting the Default Currency

Choose the Currency most commonly used by the business.

Example:

Before saving, confirm:

1. Currency Name
2. Currency Code
3. Currency Symbol
4. Payment-gateway compatibility
5. Product Prices
6. Appointment Prices

42.15 Currency Missing from the List

The customer selects from currencies already available in the platform.

When the required Currency is missing:

1. Confirm that it is not listed under another name.
2. Record its official Name.
3. Record its official three-letter Code.
4. Record its Symbol.
5. Contact the platform administrator.
6. Wait for the Currency to be added.
7. Return to Settings.
8. Select and save it.

Do not select an unrelated Currency merely because it uses the same symbol.

42.16 Organization User Currency Restrictions

An organization user may be instructed to contact the organization administrator to add or change Currency settings.

The primary organization account should manage account-wide monetary configuration so that assigned users do not create conflicting Prices or payment behavior.

Currency Display Settings

42.17 Currency Position

The account can control whether the Currency Symbol appears before or after the amount.

Symbol before the amount

Symbol behind the amount

The interface includes a Show Currency Behind setting for this purpose.

42.18 Choosing Currency Position

Use the position commonly expected by the business’s customers.

Examples:

Review the selected position throughout the public VCard rather than only inside Settings.

42.19 Hide Decimal Values

The Hide Decimal Values option controls whether decimal places are displayed.

Decimal values shown

Decimal values hidden

This should be treated primarily as a presentation setting.

42.20 Hiding Decimals Does Not Necessarily Change the Stored Price

Suppose a Product contains:

Hiding decimal values may change how the amount appears publicly, but it should not be assumed to change the stored amount or the value sent to checkout.

Test the actual gateway charge whenever Products use cents or other fractional units.

42.21 Default Currency Format

The account includes a Default Currency Format setting.

This can influence how monetary values are presented across applicable pages.

After changing it, review:

42.22 Currency Formatting and Templates

Different VCard templates may display the same Currency differently because of:

1. Layout
2. Font
3. Spacing
4. Price-card design
5. Symbol positioning
6. Decimal formatting

Test the active public template after changing Currency settings.

Assigning Currency to a Product

42.23 Opening the Product Editor

To set a Product’s Currency:

1. Select VCards.
2. Locate the intended VCard.
3. Select Edit.
4. Open Products.
5. Add a new Product or edit an existing one.
6. Locate Price.
7. Locate Currency.
8. Enter the approved amount.
9. Select the Currency.
10. Save the Product.

The system provides separate customer operations for creating, editing, updating, and deleting VCard Products.

42.24 Product Price

Enter the numerical Price without inserting explanatory text into a numerical field.

Correct:

Avoid:

The Currency selector supplies the monetary identity.

42.25 Product Currency Is Required with a Price

A Product with a Price should have a Currency.

Incomplete:

Complete:

A missing Currency can prevent checkout or cause an unclear customer experience.

42.26 Free Products

When a Product is free, confirm how the installed Product form and public template handle a zero Price.

Possible approaches include:

Do not configure a payment gateway for a free Product unless the workflow intentionally requires checkout.

42.27 Updating an Existing Product Currency

To change a Product from one Currency to another:

1. Record the current Price and Currency.
2. Calculate the approved new amount outside Book.
3. Edit the Product.
4. Change the Currency.
5. Replace the Price.
6. Save.
7. Open the public VCard.
8. Review the Product.
9. Start a new checkout session.
10. Confirm the gateway amount and Currency.

42.28 Do Not Reuse an Old Cart After a Currency Change

A browser can retain older Product or checkout information.

After changing Price or Currency:

1. Close the old checkout.
2. Refresh the VCard.
3. Open a private browser window.
4. Add the Product again.
5. Confirm the new amount.
6. Continue the controlled test.

42.29 Historical Product Orders

Changing a Product’s current Price or Currency should not be used to reinterpret a historical transaction.

Review an older order using its original:

Currency and Payment-Gateway Compatibility

42.30 Why Compatibility Matters

A Currency may be available in Book but unsupported by a particular gateway.

Possible outcomes include:

1. Payment option does not open
2. Unsupported Currency error
3. Gateway rejects the request
4. Customer is returned to the VCard
5. Transaction remains incomplete
6. Checkout displays another error

Always test the selected Currency with every enabled gateway.

42.31 PhonePe Currency

The programmed Product and Appointment workflows require:

for PhonePe.

A non-INR checkout produces a PhonePe unsupported-Currency response.

42.32 PayFast Currency

The programmed PayFast workflow requires:

Do not enable PayFast for a Product or paid Appointment using another Currency without changing the business setup appropriately.

42.33 Cashfree Currency

The programmed Cashfree Product and Appointment workflows require:

A Product using USD, EUR, or another Currency will not complete through the programmed Cashfree process.

42.34 Iyzico Currencies

The programmed Product and Appointment workflows permit the following Iyzico currencies:

A Currency outside this list produces an unsupported-Currency response in the installed workflow.

42.35 Flutterwave Currencies

The programmed Flutterwave workflow checks against this supported list:

The merchant account, country, and current Flutterwave configuration may introduce additional practical restrictions.

42.36 Paystack Currencies

Paystack uses the application’s Paystack-supported-Currency list.

Do not assume that every Book Currency is accepted.

Test the exact Currency through the merchant account and public checkout.

42.37 PayPal Currencies

PayPal uses the application’s PayPal-supported-Currency list.

An unsupported Currency produces a PayPal-specific error.

The business’s PayPal account country and merchant settings can also affect availability.

42.38 Mercado Pago Currency

Mercado Pago availability depends on the merchant account, operating country, integration configuration, and transaction Currency.

Complete a controlled test with the intended merchant account before offering it publicly.

42.39 Stripe and Razorpay Currency Testing

Stripe and Razorpay can support multiple currencies, but support depends on:

1. Merchant-account country
2. Settlement configuration
3. Payment method
4. API account
5. Transaction type
6. Gateway rules

Do not rely solely on the presence of a Currency in Book.

Understanding Payment Configuration

42.40 What Payment Configuration Does

Payment Configuration stores the account owner’s gateway credentials and activates customer-facing checkout methods.

It can support payments for:

The exact options available to a visitor depend on:

1. Saved credentials
2. Enabled configuration
3. Product or Appointment Price
4. Selected Currency
5. Supported gateway
6. Public VCard configuration

42.41 Payment Configuration Versus Platform Billing

Customer Payment Configuration is used to collect money from the VCard owner’s customers.

It is separate from payments the account owner makes to the Book platform for:

1. Platform billing
2. NFC Cards
3. Other platform purchases

Entering Stripe credentials for customer Product sales does not automatically change the payment method used to pay the Book platform.

42.42 Payment Configuration Versus Payment Links

VCard Payment Links are separate public buttons or destinations.

A Payment Link can point to:

1. Hosted invoice
2. Donation page
3. External checkout
4. Payment profile
5. Other approved payment URL

Account Payment Configuration contains gateway credentials used by programmed Product and Appointment checkout.

42.43 Opening Payment Configuration

To open it:

1. Sign in to the primary customer account.
2. Select Settings.
3. Select Payment Configuration.
4. Review the available gateway sections.
5. Open the intended gateway.
6. Enter the required credentials.
7. Select the proper mode.
8. Enable the configuration where required.
9. Select Save.

The User Settings menu links directly to the Payment Configuration section, and customer credentials are saved through the payment-method update route.

Supported Customer Payment Methods

42.44 Programmed Payment-Method List

The customer Product payment model defines:

The application contains separate success, failure, return, or checkout operations for many of these payment methods.

42.45 Gateway Availability

A gateway may not appear publicly when:

1. Its credentials are missing.
2. Its configuration is disabled.
3. The Currency is unsupported.
4. The applicable integration is incomplete.
5. The Product has no Price.
6. The Appointment is not configured as paid.
7. The account is an organization subuser.
8. The public page is cached.

42.46 Products Versus Appointments

A gateway can be implemented for both Products and Appointments, but each workflow should be tested separately.

A successful Product transaction does not prove that:

1. Appointment checkout opens correctly.
2. Appointment scheduling is recorded.
3. Appointment confirmation emails are delivered.
4. Appointment return routes work.
5. Appointment Currency is correct.

Understanding Gateway Credentials

42.47 Public Credentials

A public credential may be called:

It identifies the merchant or application during checkout.

42.48 Secret Credentials

A secret credential may be called:

It authorizes secure payment operations.

Secret credentials must be protected.

42.49 Test and Live Environments

Many gateways provide two environments.

Test, Sandbox, or Development

Used for controlled transactions without ordinary live settlement.

Live or Production

Used for real customer payments.

Use matching credentials from one environment.

42.50 Credential Mismatch

Do not combine:

Mixed credentials can cause failed sessions, invalid authentication, or unpredictable payment results.

42.51 Use This Configuration

Some payment sections may include a setting such as:

Activate it only after:

1. Required credentials are present.
2. Mode is correct.
3. Currency compatibility is confirmed.
4. Test checkout has succeeded.
5. Merchant-account verification is complete.

Payment Credential Security

42.52 Never Publish Secret Keys

Do not place gateway secrets in:

42.53 Restrict Settings Access

Only authorized account owners or organization administrators should manage payment credentials.

A staff member who processes orders does not necessarily need access to:

1. Stripe Secret
2. PayPal Secret
3. Paystack Secret
4. Flutterwave Secret
5. Razorpay Secret
6. Access Tokens
7. Merchant Passphrases

42.54 Organization User Message

An organization user may see a message directing them to contact the organization administrator to add payment credentials.

Do not share secrets through ordinary chat to bypass this control.

42.55 Two-Factor Authentication

Enable two-factor authentication where available on:

42.56 Rotating a Compromised Secret

When a secret may have been exposed:

1. Disable or rotate it at the gateway.
2. Create a replacement.
3. Update Payment Configuration.
4. Save.
5. Test the replacement.
6. Review recent gateway activity.
7. Remove the exposed value from files and messages.
8. Document the incident.

General Gateway Setup Procedure

42.57 Preparing the Merchant Account

Before configuring a gateway:

1. Create the merchant account.
2. Verify the business.
3. Complete identity requirements.
4. Add the settlement account.
5. Confirm the merchant country.
6. Confirm supported currencies.
7. Review transaction fees.
8. Review refund procedures.
9. Locate API credentials.
10. Start with Test or Sandbox mode.

42.58 Entering Credentials

1. Open Payment Configuration.
2. Locate the gateway.
3. Enter its public credential.
4. Enter its secret credential.
5. Enter additional merchant information.
6. Select Test or Live Mode.
7. Activate the configuration.
8. Save.
9. Reopen the page.
10. Confirm that the gateway remains enabled.

For security, a saved secret may be masked or omitted from the visible form.

42.59 Controlled Payment Test

1. Create a low-priced test Product.
2. Select a supported Currency.
3. Open the public VCard privately.
4. Begin checkout.
5. Confirm the gateway.
6. Confirm the Price.
7. Confirm the Currency.
8. Complete the test.
9. Wait for the return to Book.
10. Confirm the Product Order.
11. Confirm the gateway transaction.
12. Reconcile or refund the test payment.

Repeat separately for paid Appointments.

Configuring Stripe

42.60 Stripe Fields

The interface contains:

Use credentials from the same Stripe environment.

42.61 Stripe Test Setup

1. Open the Stripe merchant dashboard.
2. Enable Test Mode.
3. Copy the Publishable Key.
4. Copy the Secret Key.
5. Open Book Payment Configuration.
6. Enter both values.
7. Save.
8. Create a test Product.
9. Complete the test transaction.
10. Confirm the payment in Stripe and Book.

42.62 Moving Stripe to Live Mode

1. Complete merchant verification.
2. Retrieve the Live Publishable Key.
3. Retrieve the Live Secret Key.
4. Replace both Test credentials.
5. Save.
6. Conduct an approved low-value live transaction.
7. Confirm settlement.
8. Remove the test Product or label it appropriately.

42.63 Stripe Errors

Review:

1. Test and Live mismatch
2. Invalid or expired secret
3. Leading or trailing spaces
4. Unsupported Currency
5. Merchant-account restriction
6. Incomplete return handling
7. Browser blocking
8. Incorrect amount

Configuring PayPal

42.64 PayPal Fields

The interface includes:

The Mode and credentials must match.

42.65 PayPal Sandbox Setup

1. Open the PayPal developer dashboard.
2. Create or select an application.
3. Select Sandbox.
4. Copy the Client ID.
5. Copy the Secret.
6. Enter them in Book.
7. Select Sandbox Mode.
8. Save.
9. Use an approved Sandbox buyer account.
10. Confirm the result in both systems.

42.66 PayPal Live Setup

1. Complete PayPal merchant verification.
2. Open the Live application.
3. Copy the Live Client ID.
4. Copy the Live Secret.
5. Replace both Sandbox credentials.
6. Select Live Mode.
7. Save.
8. Test an approved live payment.

42.67 PayPal Unsupported Currency

When PayPal reports that the Currency is not supported:

1. Confirm the Product Currency.
2. Confirm the account Currency.
3. Review PayPal merchant support.
4. Change to a compatible Currency or gateway.
5. Recalculate the Price.
6. Start a new checkout.

Configuring Paystack

42.68 Paystack Fields

The interface includes:

42.69 Paystack Setup

1. Open the Paystack dashboard.
2. Select Test Mode.
3. Copy the Public Key.
4. Copy the Secret Key.
5. Enter both values in Book.
6. Review the callback destination where provided.
7. Configure the required callback in Paystack.
8. Save.
9. Complete a controlled checkout.
10. Confirm the transaction in both systems.

42.70 Paystack Callback

The callback tells Paystack where to return the payment result.

Copy it exactly.

Do not:

1. Remove the domain
2. Remove the path
3. Add spaces
4. Use an administrator page
5. Use a VCard URL
6. Mix staging and production domains

42.71 Paystack Credential Error

When the interface reports incorrect Paystack credentials:

1. Confirm Test or Live environment.
2. Copy the complete keys again.
3. Remove whitespace.
4. Confirm the merchant account is active.
5. Save.
6. Start a new checkout session.

Configuring Flutterwave

42.72 Flutterwave Fields

The interface includes:

Use matching credentials from the same environment.

42.73 Flutterwave Setup

1. Open Flutterwave.
2. Select the Test environment.
3. Copy the Public Key.
4. Copy the Secret Key.
5. Enter them in Payment Configuration.
6. Save.
7. Select a supported Currency.
8. Complete a Product test.
9. Complete an Appointment test.
10. Confirm both records.

42.74 Flutterwave Currency Error

When the selected Currency is outside the programmed list:

1. Record the Currency.
2. Review the supported list.
3. Select a compatible Currency or gateway.
4. Recalculate the Price where required.
5. Save.
6. start a new transaction.

Configuring Razorpay

42.75 Razorpay Fields

The interface includes:

42.76 Razorpay Setup

1. Open the Razorpay dashboard.
2. Use Test Mode initially.
3. Retrieve the Key ID.
4. Retrieve the Key Secret.
5. Enter both in Book.
6. Save.
7. Begin a public Product checkout.
8. Complete the test.
9. Confirm the payment in Razorpay.
10. Confirm the Book Product Order.

Test Appointment payments separately.

Configuring PhonePe

42.77 PhonePe Configuration

The PhonePe configuration uses merchant credentials such as a Merchant ID and related security information according to the installed fields.

The Product and Appointment Currency must be:

42.78 PhonePe Setup

1. Confirm the PhonePe merchant integration.
2. Obtain the required credentials.
3. Set the applicable Currency to INR.
4. Enter the credentials in Book.
5. Save.
6. Test the checkout.
7. Confirm the return result.
8. Confirm the Book transaction.

Configuring Mercado Pago

42.79 Mercado Pago Fields

The interface includes:

Treat the Access Token as a secret.

42.80 Mercado Pago Setup

1. Open the Mercado Pago developer account.
2. Select test credentials.
3. Copy the Public Key.
4. Copy the Access Token.
5. Enter them in Book.
6. Save.
7. Test the intended Currency.
8. Complete checkout.
9. Confirm the Mercado Pago transaction.
10. Confirm the Book record.

Configuring PayFast

42.81 PayFast Fields

The interface includes:

The programmed Currency requirement is:

42.82 PayFast Setup

1. Open the PayFast merchant account.
2. Select Sandbox or Live.
3. Copy the Merchant ID.
4. Copy the Merchant Key.
5. Enter the Passphrase.
6. Enter all values in Book.
7. Select the matching Mode.
8. Confirm ZAR as the Currency.
9. Save.
10. Complete a controlled transaction.

Configuring Iyzico

42.83 Iyzico Fields

The interface includes:

42.84 Iyzico Setup

1. Open Iyzico.
2. Select Sandbox.
3. Retrieve the API Key.
4. Retrieve the Secret Key.
5. Enter both in Book.
6. Select Sandbox Mode.
7. Use a supported Currency.
8. Save.
9. Complete a controlled transaction.
10. Confirm the records.

Configuring Cashfree

42.85 Cashfree Fields

The interface includes:

The programmed Currency requirement is:

42.86 Cashfree Setup

1. Open Cashfree.
2. Select Test or Sandbox.
3. Retrieve the App ID.
4. Retrieve the Secret.
5. Enter them in Book.
6. Select the matching Mode.
7. Confirm INR.
8. Save.
9. Test Product checkout.
10. Test Appointment checkout.

Configuring Manual Payment

42.87 Understanding Manual Payment

Manual Payment allows a customer to place a Product Order or Appointment request using an offline payment process.

Examples:

The transaction requires human verification.

42.88 Manual Payment Request

The programmed Product workflow can create a transaction containing:

Notifications can also be sent to the customer and VCard owner when the applicable email settings are enabled.

42.89 Manual Payment Guide

Manual-payment instructions should explain:

Avoid displaying more banking information than is required.

42.90 Customer Manual-Payment Process

The customer generally:

1. Selects Manual Payment.
2. Reviews the instructions.
3. Sends the required amount.
4. Records the transaction reference.
5. Completes the Product or Appointment form.
6. Sends proof where requested.
7. Waits for verification.

42.91 Verifying a Manual Payment

The business should:

1. Locate the request.
2. Confirm the customer.
3. Confirm the amount.
4. Confirm the Currency.
5. Confirm the payment reference.
6. Verify the money directly in the receiving account.
7. Check for reversal.
8. Update the order or Appointment.
9. Notify the customer.

Do not approve a payment based only on a screenshot.

42.92 Pending Manual Payment

A Manual Payment can remain pending until authorized staff complete verification.

Do not deliver a paid Product or confirm a paid Appointment merely because the request exists.

Enabling Payments for Products

42.93 Product Checkout Preparation

Before publishing a paid Product:

1. Confirm the Product Name.
2. Confirm the Price.
3. Confirm the Currency.
4. Confirm the description.
5. Configure at least one gateway.
6. Test Currency compatibility.
7. Save.
8. Open the public VCard.
9. Start checkout.
10. Confirm the displayed methods.

42.94 Customer Information

Product checkout can request information such as:

The exact required fields depend on the installed Product checkout.

42.95 Product Order Records

A successful payment should be compared across:

Do not rely on only the browser success message.

42.96 Product Transaction Currency

The Product checkout uses:

1. The Product’s own Currency when assigned.
2. The account default Currency when the Product Currency is not assigned.

Review both locations when checkout uses an unexpected Currency.

Enabling Payments for Appointments

42.97 Paid Appointment Preparation

Before accepting paid Appointments:

1. Configure Appointment availability.
2. Configure applicable Services.
3. Enter the Price.
4. Select the correct account Currency.
5. Configure a compatible gateway.
6. Enable paid booking.
7. Test available dates and times.
8. Complete a controlled payment.
9. Confirm the Appointment.
10. Confirm the gateway transaction.

42.98 Appointment and Payment Are Separate Records

A booking can potentially exist while its payment is:

Staff should confirm both the Appointment and payment state.

42.99 Payment Succeeds but Appointment Is Missing

Review:

1. Gateway transaction
2. Return URL
3. Appointment callback
4. Customer email
5. Selected date and time
6. Book Appointment list
7. Payment Status page
8. Browser interruption

Do not request another payment until the first transaction is verified.

Payment Statuses

42.100 Pending

Pending means the payment has not been fully confirmed.

Possible reasons include:

1. Manual verification required
2. Gateway response delayed
3. Customer closed checkout
4. Callback incomplete
5. Transaction still processing

42.101 Successful or Paid

Successful or Paid means Book has recorded a successful result.

For higher-value transactions, also confirm:

1. Gateway status
2. Amount
3. Currency
4. Customer
5. Settlement or authorization
6. Transaction ID

42.102 Failed

Failed means the transaction did not complete successfully.

Possible causes include:

42.103 Cancelled

Cancelled can indicate that:

1. The customer cancelled checkout.
2. The payment page was closed.
3. The session expired.
4. The gateway returned a cancellation.
5. The customer returned without paying.

Do not fulfill a paid item based on a cancelled transaction.

Transaction Reconciliation

42.104 What Reconciliation Means

Reconciliation confirms that Book and the payment gateway agree.

Compare:

42.105 Daily Reconciliation

During active sales:

1. Review new Product Orders.
2. Review paid Appointments.
3. Open the gateway dashboard.
4. Match transaction IDs.
5. Confirm amounts.
6. Confirm currencies.
7. Identify Pending or failed records.
8. Investigate discrepancies.
9. Record refunds.
10. Release fulfillment only after verification.

42.106 Transaction ID

The Transaction ID is a gateway reference used to identify a payment.

Protect it as business transaction information.

Do not post it publicly or include it in unrelated communications.

42.107 Payment Date

When comparing records, consider:

1. Book account time zone
2. Gateway time zone
3. Customer time zone
4. Delayed callback
5. Midnight date changes

Two records can refer to the same transaction while displaying slightly different local dates or times.

Refunds

42.108 Refund Procedure

Refunds are generally processed through the applicable gateway unless Book provides a specific refund action for that transaction.

Recommended process:

1. Locate the Book order or Appointment.
2. Locate the gateway transaction.
3. Confirm the customer.
4. Confirm the amount and Currency.
5. Review the refund policy.
6. Initiate the refund.
7. Save the refund reference.
8. Update internal records.
9. Notify the customer.
10. Reconcile the settlement.

42.109 Partial Refunds

When a partial refund is permitted:

1. Confirm the original amount.
2. Confirm the refundable amount.
3. Confirm the Currency.
4. Document the reason.
5. Process it through the gateway.
6. Record the remaining retained amount.
7. Notify the customer clearly.

42.110 Manual-Payment Refund

A Manual Payment normally must be refunded through the original offline method.

Record:

42.111 Do Not Change Currency to Create a Refund

Changing a Product Currency or account Currency does not reverse an existing payment.

A refund must reference the original transaction.

Gateway and Currency Testing

42.112 Complete Gateway Test Matrix

For each enabled gateway, test:

42.113 Test One Gateway at a Time

When several gateways are configured:

1. Enable one gateway.
2. Test it completely.
3. Record the result.
4. Correct errors.
5. Proceed to the next gateway.

This makes it easier to identify which configuration caused a problem.

42.114 Low-Value Live Test

After Sandbox testing, conduct an authorized low-value live transaction before public launch.

Confirm:

1. Real checkout
2. Correct Currency
3. Correct amount
4. Merchant receipt
5. Book record
6. Customer confirmation
7. Refund process where appropriate

Troubleshooting Currency Settings

42.115 Currency Selector Is Empty

Confirm that:

1. The page loaded completely.
2. The account has currency access.
3. The platform has active Currency records.
4. The browser is current.
5. Search or filters are cleared.
6. The organization administrator configured Currency.

42.116 Wrong Currency Symbol Appears

Review:

1. Product-specific Currency.
2. Account default Currency.
3. Currency Code.
4. Currency Symbol.
5. Browser cache.
6. Duplicated Product settings.
7. Active VCard template.

42.117 Correct Symbol but Wrong Price

Changing Currency does not convert the amount.

Edit the Price manually.

42.118 Product Reports Currency Required

1. Edit the Product.
2. Confirm a Price is present.
3. Select a Currency.
4. Save.
5. Reopen the Product.
6. Confirm the selection remains.
7. Test the public page.

42.119 Currency Appears in the Wrong Position

Review Show Currency Behind or the applicable Currency-position control.

Save and test again.

42.120 Decimal Values Are Incorrect

Review:

Do not rely only on the Product card.

42.121 Gateway Rejects the Currency

1. Record the gateway.
2. Record the Currency Code.
3. Review programmed gateway restrictions.
4. Review the merchant account.
5. Select a compatible Currency or gateway.
6. Recalculate the Product Price.
7. Save.
8. Begin a new checkout.

Troubleshooting Payment Configuration

42.122 Payment Configuration Is Missing

Confirm that:

1. The primary account is signed in.
2. Settings loaded completely.
3. Payment Configuration was selected.
4. The organization administrator has access.
5. The customer User Settings routes are available.

42.123 Payment Option Does Not Appear Publicly

Confirm:

1. Gateway credentials are saved.
2. Gateway is enabled.
3. Mode is selected.
4. Product has a Price.
5. Product has a Currency.
6. Appointment is configured as paid.
7. VCard is active.
8. Currency is supported.
9. Public page was refreshed.

42.124 “Please Add Payment Credentials”

This means the selected payment option lacks required credentials.

1. Open Payment Configuration.
2. Locate the gateway.
3. Complete every required field.
4. Select the proper mode.
5. Enable the configuration.
6. Save.
7. Test again.

42.125 Credentials Are Rejected

Check:

42.126 Payment Page Does Not Open

Confirm:

1. Payment Method is selected.
2. Browser allows redirects and popups.
3. Internet connection is stable.
4. Required customer fields are complete.
5. Currency is supported.
6. Credentials are correct.
7. The gateway is operating.
8. The button was selected once.

42.127 Wrong Amount at Checkout

Review:

1. Product Price
2. Appointment Price
3. Quantity
4. Currency
5. Decimal settings
6. Taxes or additional charges
7. Cached checkout session
8. Correct Product record

Stop the transaction until the amount is correct.

42.128 Wrong Currency at Checkout

Review:

1. Product-specific Currency.
2. Account default Currency.
3. Old browser session.
4. Gateway support.
5. Correct Product.
6. Correct VCard.

Open a fresh private session after corrections.

42.129 Test Credentials Charge Real Money

Stop using the configuration.

Confirm:

1. Credential prefixes
2. Merchant environment
3. Mode
4. Whether Live keys were entered
5. Whether the gateway’s test switch is active

42.130 Live Credentials Produce a Test Checkout

Confirm:

1. Live Mode is selected.
2. Both credentials are Live.
3. Production callback is configured.
4. Merchant account is approved.
5. Public VCard is on the production domain.
6. An older test session is not being reused.

Troubleshooting Payment Results

42.131 Payment Succeeds but Book Shows Pending

1. Do not charge the customer again.
2. Save the gateway receipt.
3. Record the Transaction ID.
4. Refresh Book.
5. Review the callback or return route.
6. Confirm the correct merchant account.
7. Contact support with both records.
8. Fulfill only after verification.

42.132 Book Shows Paid but Gateway Does Not

Treat the payment as unverified.

Check:

1. Test versus Live dashboard
2. Transaction ID
3. Correct merchant account
4. Manual-payment approval
5. Reversed payment
6. Manually changed Book status

42.133 Customer Was Charged Twice

1. Locate both gateway transactions.
2. Locate both Book orders.
3. Compare timestamps.
4. Compare amounts.
5. Stop duplicate fulfillment.
6. Refund the duplicate according to policy.
7. Retain both references.
8. Investigate repeated submission.

42.134 Customer Closed the Browser After Payment

Before requesting payment again:

1. Check the gateway.
2. Check Product Orders or Appointments.
3. Search by customer email.
4. Refresh the dashboard.
5. Wait for delayed callback processing.
6. Contact support when records disagree.

42.135 Callback or Return URL Error

Confirm:

42.136 Payment Page Is Blank

Try:

1. Private browsing
2. Another browser
3. Disabling blocking extensions
4. Confirming JavaScript
5. Checking gateway availability
6. Reviewing credentials
7. Reviewing Currency
8. Creating a new checkout session

Troubleshooting Manual Payments

42.137 Manual Payment Does Not Appear

Confirm:

1. Manual Payment is enabled.
2. Instructions are configured.
3. Product or Appointment permits payment.
4. Public page is refreshed.
5. Account administrator saved the configuration.

42.138 Manual Payment Remains Pending

This is expected until authorized staff verify the payment.

Check the receiving account directly.

42.139 Manual Payment Was Approved Incorrectly

1. Recheck the receiving account.
2. Pause fulfillment.
3. Contact the customer.
4. Correct the transaction status.
5. Record who approved it.
6. Review the verification procedure.
7. Require direct account verification in the future.

42.140 Fake Proof of Payment

Do not rely solely on:

Verify the payment through the receiving bank, wallet, or approved financial account.

Payment Privacy and Recordkeeping

42.141 Do Not Collect Raw Card Details

Customers should enter card details only through the payment gateway’s secure checkout.

Do not request raw payment-card information through:

42.142 Protect Transaction Records

Payment records can contain:

Restrict them to authorized staff.

42.143 Retention

Retain payment records according to:

1. Accounting needs
2. Tax requirements
3. Refund periods
4. Dispute periods
5. Privacy Policy
6. Merchant agreement
7. Applicable laws

Do not retain sensitive information unnecessarily.

42.144 Downloaded Invoices

Store downloaded invoices in an approved business-records location.

Avoid:

1. Public cloud links
2. Shared personal devices
3. Unrestricted email attachments
4. Public team channels
5. Open Downloads folders

Recommended Operational Process

42.145 Initial Configuration

Use this order:

42.146 Daily Payment Review

During active sales:

1. Review Product Orders.
2. Review paid Appointments.
3. Review Pending transactions.
4. Compare gateway records.
5. Investigate failures.
6. Confirm Manual Payments.
7. Process refunds.
8. protect customer information.

42.147 Monthly Configuration Review

Each month:

1. Review enabled gateways.
2. Confirm Currency remains correct.
3. Review Product currencies.
4. Review Appointment Prices.
5. Review gateway users.
6. Review callbacks.
7. Review failed transactions.
8. Review refunds.
9. Rotate exposed credentials.
10. Remove obsolete payment methods.

Currency Checklist

42.148 Final Currency Checklist

Before accepting payments, confirm that:

1. The correct default Currency is selected.
2. The Currency Name is correct.
3. The Currency Code is correct.
4. The Currency Symbol is correct.
5. Currency position is correct.
6. Decimal display is correct.
7. Product-specific currencies are reviewed.
8. Product Prices match their currencies.
9. Appointment Prices are correct.
10. Currency changes were not mistaken for conversions.
11. The gateway supports the Currency.
12. Historical transactions remain documented.
13. Public Product display was tested.
14. Checkout Currency was tested.
15. Invoice Currency was tested.

Payment Configuration Checklist

42.149 Final Payment Checklist

Confirm that:

1. The primary account owner manages credentials.
2. The merchant account is verified.
3. Settlement information is complete.
4. The correct gateway is selected.
5. Public and secret credentials match.
6. Test or Live Mode is correct.
7. Callback or return URLs are correct.
8. The configuration is enabled.
9. Currency compatibility is confirmed.
10. Product checkout was tested.
11. Appointment checkout was tested.
12. Manual Payment instructions are complete.
13. Successful payment was tested.
14. Failed payment was tested.
15. Cancelled payment was tested.
16. Book and gateway records match.
17. Refund procedures are documented.
18. Secret credentials are protected.
19. Staff understand Pending, Paid, Failed, and Cancelled statuses.
20. Customer payment information is not collected through unsecured fields.

Chapter Completion

At the end of this chapter, the user should understand how to select and format the account Currency, assign Product-specific currencies, avoid treating a Currency change as an automatic exchange-rate conversion, configure Stripe, PayPal, Paystack, PhonePe, Flutterwave, Razorpay, Mercado Pago, PayFast, Iyzico, Cashfree, and Manual Payment, protect gateway credentials, test Product and Appointment checkout, reconcile gateway transactions, process refunds, and troubleshoot unsupported currencies, missing payment options, credential errors, callback failures, duplicate charges, and pending transactions.