41.1 Overview

This chapter explains three account-wide settings that affect how the Book system operates:

1. Storage Management shows how much media storage the account has used and how much remains available.
2. Currencies control how prices and monetary amounts are displayed throughout VCards, products, appointments, orders, and related payment areas.
3. Payment Methods connect the account to payment gateways that allow visitors to pay for products or appointments through public VCards.

These settings work across multiple VCards. A change made at the account level can therefore affect more than one public card.

The customer dashboard includes a dedicated Storage menu and a separate Settings area. Storage opens through the user.storage destination, while account configuration opens through user.setting.index.

The customer-side routes also contain separate operations for viewing user settings, opening Payment Methods, saving general settings, and saving payment credentials.

Part One: Storage Management

41.2 Understanding Account Storage

Storage is the space used by media uploaded to the Book system.

Uploaded media can include:

Storage is generally measured in megabytes, displayed as MB.

The account’s Storage page helps the user understand:

41.3 Opening Storage

To open the Storage page:

1. Sign in to the customer dashboard.
2. Locate Storage in the main navigation.
3. Select Storage.
4. Wait for the usage information to load.
5. Review the Used and Unused amounts.

The customer menu places Storage immediately before Settings and connects it to the user.storage route.

41.4 Storage Is an Account-Level Summary

Storage is calculated for the account rather than for only the VCard currently being edited.

Media uploaded to several VCards can contribute to the same account total.

Example:

The Storage page should therefore be reviewed as an overall account-usage report.

41.5 Used Storage

Used Storage represents the amount of the account’s assigned storage currently occupied by uploaded media.

Example:

This means uploaded account media currently occupies approximately 175 MB.

41.6 Unused Storage

Unused Storage represents the remaining available amount.

Basic calculation:

Example:

Unused Storage is the space that remains available for new uploads.

41.7 Storage Used Percentage

The displayed percentage can be calculated as:

Example:

This indicates that 35 percent of the assigned storage is currently occupied.

41.8 Storage Limit

The Storage Limit is the maximum amount of uploaded media the account can retain.

The programmed interface describes the limit in megabytes and states that a user cannot upload media beyond the entered storage size.

When storage is exhausted, new media uploads may be rejected until:

1. Existing media is removed.
2. Smaller media is uploaded.
3. Additional storage is assigned.
4. Unnecessary content is deleted.

41.9 Storage Is Not a General Cloud Drive

The Storage page should not be treated as a general file-management service.

It is primarily a usage-monitoring area for media stored through Book features.

The inspected customer interface does not establish the Storage page as a normal folder browser with functions such as:

Media should ordinarily be managed through the feature where it was originally uploaded.

41.10 Removing Media Through Its Original Feature

To remove storage-consuming media, return to the applicable feature.

Examples:

This helps preserve the relationship between the database record and its media file.

41.11 Do Not Delete Media Directly from the Server

A customer should not attempt to free storage by deleting files directly through:

Direct deletion can leave database records pointing to missing files.

This can cause:

1. Broken images
2. Blank product thumbnails
3. Missing public content
4. Error messages
5. Incorrect usage calculations
6. Media-library inconsistencies

Use the Book dashboard’s normal Delete, Remove, or Replace operation.

Understanding What Uses Storage

41.12 VCard Profile Images

Each VCard can contain a Profile Image.

When several VCards use separately uploaded copies of the same image, each stored file may contribute to the account total.

Instead of uploading multiple oversized copies:

1. Prepare one optimized version.
2. Use consistent dimensions.
3. Upload only where needed.
4. Remove old images after replacements are verified.

41.13 Cover Images

Cover images are often wider and larger than profile images.

They can consume substantial storage when:

1. Uploaded at camera resolution
2. Saved with little compression
3. Replaced frequently
4. Duplicated across many VCards
5. Stored as large PNG files

The VCard cover-image interface accepts uploaded image media and provides a preview and cropping process.

41.14 Favicon Images

A favicon is normally small, but repeated oversized favicon uploads can still contribute to unnecessary storage use.

Prepare favicons at an appropriate size rather than uploading a large company logo and relying only on browser scaling.

41.15 Service Images

Each VCard Service can include an image.

To control storage:

1. Remove abandoned Services.
2. Replace unnecessarily large photographs.
3. Avoid uploading the same image several times during testing.
4. Verify the new image before deleting the old Service.
5. Retain originals outside Book when they are business assets.

41.16 Product Images

Products can contain one or more media records.

Product media can become one of the largest storage categories when the account contains:

1. Large catalogs
2. Multiple images per product
3. High-resolution photography
4. Duplicate products
5. Old products no longer sold

The source includes a customer operation for deleting individual Product media and separate operations for creating, updating, and deleting Products.

41.17 Gallery Media

Gallery images and uploaded gallery content can consume storage quickly because a gallery often contains several items.

Before uploading an entire gallery:

1. Remove duplicate photographs.
2. Resize excessively large images.
3. Compress web images.
4. Use only the strongest approved content.
5. Confirm that every item supports the VCard’s purpose.

41.18 Blog Images

Blog cover images and other uploaded Blog media can remain in the account even after a campaign is no longer active.

Periodically review:

1. Draft Blogs
2. Old event announcements
3. Duplicate articles
4. Temporary promotional Blogs
5. Blogs connected to deleted campaigns

Do not delete a Blog image without confirming whether the Blog remains public.

41.19 Testimonial Images

Testimonial profile photographs are usually displayed at relatively small dimensions.

Uploading a multi-megabyte portrait for a small testimonial image creates unnecessary storage use.

Prepare a web-sized image before uploading.

41.20 Banner Images

Banners are normally wide and may be created at high resolution.

Review old Banners connected to:

1. Expired sales
2. Past events
3. Discontinued offers
4. Seasonal campaigns
5. Old landing pages

Delete or replace them through the VCard Banner section.

41.21 WhatsApp Store Media

WhatsApp Stores can include:

A large product catalog can use more storage than an ordinary VCard.

Storage maintenance should therefore include both VCards and WhatsApp Stores.

41.22 Virtual Background Downloads

A Virtual Background generated and downloaded to the user’s computer is not automatically the same as a permanent customer media upload.

The source Front Image, Back Image, and Logo used during Custom generation may be processed in the browser for the download workflow.

The user should still manage the downloaded ZIP and PNG files on their own device because the Book Storage page is not intended to manage local computer files.

41.23 External URLs and Embedded Content

Content displayed through an external URL generally does not consume the same local storage as a file uploaded directly into Book unless the application creates and retains a local copy.

Examples can include:

1. YouTube embeds
2. Instagram embeds
3. LinkedIn embeds
4. External Product URLs
5. External website links
6. Iframes

The external platform stores the primary content, while Book stores the associated link or embed information.

File Size and Image Dimensions

41.24 File Size Is Different from Image Dimensions

Image dimensions describe width and height.

Example:

File size describes how much storage space the file occupies.

Example:

Two images with identical dimensions can have very different file sizes based on:

1. File format
2. Compression
3. Image detail
4. Transparency
5. Metadata
6. Export quality

41.25 Common Image Formats

JPG or JPEG

Usually appropriate for photographs.

Advantages:

1. Smaller size
2. Good photo compression
3. Broad compatibility

Limitations:

1. No transparent background
2. Repeated editing can reduce quality

PNG

Often appropriate for logos, graphics, and transparency.

Advantages:

1. Supports transparency
2. Sharp graphic edges
3. High visual quality

Limitations:

1. Can be much larger than JPG

WebP

Often provides good web quality at a smaller size.

Advantages:

1. Efficient compression
2. Supports transparency
3. Useful for web delivery

Limitations:

1. Confirm compatibility with the applicable upload field and downstream use

GIF

Can support animation but may become large and may not be appropriate for every section.

41.26 Recommended Optimization Workflow

Before uploading:

1. Open the original image in an image editor.
2. Crop unused areas.
3. Resize it for its intended display.
4. Export using an appropriate format.
5. Reduce quality only enough to lower file size without making it visibly poor.
6. Remove unnecessary metadata where appropriate.
7. Save the original separately.
8. Upload the optimized copy.
9. Preview the public VCard.

41.27 Avoid Uploading Camera Originals

A modern phone photograph may be:

A public VCard may display that photograph at only a few hundred pixels wide.

Uploading the original can waste storage and slow the page.

Create a web-optimized version first.

Reviewing and Reducing Storage

41.28 Recommended Monthly Storage Review

At least once each month:

1. Open Storage.
2. Record Used Storage.
3. Compare it with the previous review.
4. Identify recently added media.
5. Review inactive VCards.
6. Review old Products.
7. Review old Galleries.
8. Review expired Banners.
9. Review WhatsApp Store catalogs.
10. Remove verified obsolete media.
11. Reopen Storage and confirm the result.

41.29 Start with the Largest Categories

When storage is nearly full, begin with areas likely to contain the largest files:

Deleting several tiny favicons is less effective than replacing one oversized product catalog.

41.30 Review Inactive VCards

An inactive VCard may still retain its uploaded media.

Deactivating a VCard normally controls public availability. It should not be assumed to delete the card’s media.

Review inactive VCards and decide whether they should be:

1. Reactivated
2. Archived externally
3. Duplicated for future use
4. Permanently deleted

41.31 Deleting a VCard

Deleting a VCard is a major action.

It can remove or disconnect:

Do not delete an entire VCard merely to remove one large image.

Use the media-specific edit operation when possible.

41.32 Back Up Important Assets

Before deleting business media:

1. Confirm that an original copy exists.
2. Download or retrieve the approved source asset.
3. Store it in an organized business folder.
4. Record which VCard used it.
5. Confirm that it is no longer needed publicly.
6. Delete it through the dashboard.
7. Test the public VCard.

Book Storage should not be treated as the only copy of a business’s original brand assets.

41.33 Storage May Not Update Instantly

After replacing or deleting media:

1. Refresh the Storage page.
2. Sign out and back in when necessary.
3. Allow the application to recalculate usage.
4. Confirm that the old media record was actually removed.
5. Check whether duplicate media remains elsewhere.

A delayed display does not necessarily mean the deletion failed.

41.34 Storage and Organization Users

The primary account owner or organization administrator should coordinate storage usage across assigned users.

An organization user may be able to upload media to an assigned VCard while the storage allowance is controlled at the parent account level.

Good internal procedures include:

1. Approved image dimensions
2. Maximum working file sizes
3. Naming standards
4. Duplicate-content rules
5. Periodic media review
6. Administrator approval for large catalogs

Storage Security and Privacy

41.35 Do Not Upload Confidential Files as Public Media

VCard and Store media can become publicly accessible.

Do not upload:

Even when a file is later removed from the visible VCard, copies may remain in browser caches, downloads, backups, or screenshots.

41.36 Remove Embedded Sensitive Information

Photographs and documents can contain:

1. GPS metadata
2. Author names
3. Device information
4. Hidden document properties
5. Private background information
6. Visible addresses or account numbers

Review media before uploading.

41.37 Use Approved Brand Assets

Store only assets the account has the right to use.

Avoid uploading:

1. Copyrighted photographs without permission
2. Unlicensed stock images
3. Third-party logos without approval
4. Customer photographs without consent
5. Employee images without authorization

Storage Troubleshooting

41.38 Storage Page Does Not Open

Try:

1. Refreshing the dashboard.
2. Signing out and back in.
3. Confirming the main customer account is being used.
4. Clearing outdated browser cache.
5. Opening a private browser window.
6. Trying another supported browser.
7. Reporting the exact error to the administrator.

41.39 Storage Menu Is Missing

Confirm that:

1. The customer dashboard loaded completely.
2. The account has the correct customer role.
3. The user is not inside a restricted organization-user context.
4. The installation’s menu files are current.
5. The browser is not displaying an old cached sidebar.

The installed primary customer menu contains Storage as a dedicated item.

41.40 Used Storage Appears Too High

Review:

1. Duplicate VCards
2. Duplicate Products
3. Product media galleries
4. WhatsApp Store products
5. Old Blog images
6. Old Gallery records
7. Replaced Cover Images
8. Inactive VCards
9. Old Banners

A visually hidden or inactive record may still retain media.

41.41 Used Storage Appears Too Low

Possible reasons include:

1. Some media is externally hosted.
2. The usage report has not recalculated.
3. A file upload did not complete.
4. Certain temporary files are not counted.
5. Media is associated with another account.
6. A browser preview is showing a cached external image.

41.42 Upload Is Rejected Because Storage Is Full

1. Open Storage.
2. Confirm Used and Unused amounts.
3. Identify the largest unnecessary media.
4. Back up important originals.
5. Delete obsolete media through its source feature.
6. Refresh Storage.
7. Optimize the new upload.
8. Attempt the upload again.

Do not repeatedly upload the same file while the account is full.

41.43 Image Was Deleted but Still Appears

The browser may have cached the old image.

Try:

1. Refreshing the public VCard.
2. Opening a private window.
3. Clearing browser cache.
4. Checking the record in the editor.
5. Confirming that the correct VCard was edited.
6. Waiting for any content-delivery cache to update.

41.44 Image Is Missing After Cleanup

The deleted file may still have been in use.

Check:

1. VCard Basic Details
2. Product
3. Service
4. Gallery
5. Blog
6. Testimonial
7. Banner
8. WhatsApp Store

Restore the approved original through the applicable edit screen.

Part Two: Currencies

41.45 Understanding Currency Configuration

Currency configuration determines how monetary amounts are identified and displayed.

A currency record can contain information such as:

Examples:

41.46 Currency Does Not Automatically Convert Prices

Changing a currency selection does not automatically convert the numerical value.

Example:

The system should not be assumed to calculate an exchange rate merely because the currency was changed.

The account owner must enter the correct amount for the selected currency.

41.47 Account Default Currency

The account can use a default currency setting.

This default can be used when a transaction, appointment, or product does not have a more specific currency assigned.

The public VCard controller retrieves the account’s currency_id setting and uses it with the configured payment methods. This makes currency an important account-wide payment dependency.

41.48 Opening Currency Settings

To review the customer currency:

1. Sign in to the dashboard.
2. Open Settings.
3. Open the General settings section.
4. Locate Currency or Select Currency.
5. Choose the intended default.
6. Review currency-format settings.
7. Save the changes.
8. Test a public VCard.

The customer Settings area and Payment Configuration are managed through the customer-side User Settings routes.

41.49 Available Currencies

Customers select from currencies already available in the platform.

The normal customer settings area is not the same as the platform’s currency-administration area.

A customer should not assume they can create a new currency code directly.

When the required currency is missing:

1. Confirm that it is not listed under another name.
2. Record the official currency name, code, and symbol.
3. Contact the platform administrator.
4. Wait for the currency to be added.
5. Return to Settings and select it.

41.50 Currency Code

The currency code is normally a three-letter identifier.

Examples:

The code is important because payment gateways frequently validate the code rather than only the displayed symbol.

41.51 Currency Icon or Symbol

The currency icon is the visual symbol displayed near an amount.

Examples:

A symbol can be ambiguous.

For example, $ can represent several dollar-based currencies. Where confusion is possible, confirm the currency code in the checkout, invoice, or product description.

41.52 Currency Position

Currency Position controls whether the symbol appears before or after the amount.

Currency before amount

Currency behind amount

The interface includes a Show Currency Behind option for changing this presentation.

41.53 Hide Decimal Values

The Hide Decimal Values setting controls whether amounts are visually displayed with decimal places.

Decimals shown

Decimals hidden

This is primarily a display choice.

It should not be assumed to change a stored value from 100.50 to 100.

41.54 Decimal Display and Payment Amount

When decimal values are hidden, review the actual amount sent to the payment gateway.

A product entered as:

could display differently when decimal hiding is enabled.

Always test the complete checkout rather than relying only on the public product card.

41.55 Default Currency Format

The platform includes a Default Currency Format setting.

This can control the account’s standard monetary presentation.

After changing the format, review:

1. Public VCard Products
2. Appointment pricing
3. Product checkout
4. Orders
5. Invoices
6. Payment confirmations
7. Manual-payment instructions

Product-Level Currency

41.56 Assigning Currency to a VCard Product

VCard Products have their own Currency selector.

To select it:

1. Open VCards.
2. Edit the intended VCard.
3. Open Products.
4. Add a Product or edit an existing one.
5. Enter the Price.
6. Select the Currency.
7. Save.
8. Preview the public Product.

The customer routes include separate VCard Product creation, editing, updating, and deletion operations.

41.57 Currency Is Required with Product Price

When a Product has a Price, the Currency must also be selected.

A price without a currency creates ambiguity.

Example of an incomplete Product:

Correct example:

41.58 Product Currency Can Override the Account Default

A Product can have its own currency_id.

When the Product has a currency, its checkout uses that Product currency.

When the Product does not have its own currency, the system can fall back to the VCard owner’s account currency setting.

This allows different Products to use a specific currency while maintaining an account-wide default.

41.59 Use One Consistent Currency Where Possible

Using several currencies in one VCard can confuse visitors.

Example:

Multiple currencies may be appropriate for a specific international business, but they require:

1. Clear labeling
2. Compatible payment gateways
3. Accurate pricing
4. Separate accounting
5. Careful refund handling

Use one primary currency unless there is a clear reason not to.

41.60 Changing an Existing Product Currency

To change a Product currency safely:

1. Review the current Price and Currency.
2. Calculate the correct new price outside the system.
3. Edit the Product.
4. Select the new Currency.
5. Enter the converted or approved amount.
6. Save.
7. Preview the public Product.
8. Complete a controlled checkout test.
9. Confirm the gateway charged the correct currency.

Do not change only the currency symbol.

41.61 Historical Orders

Changing the current Product currency should not be used to reinterpret an older completed order.

Historical records should be reviewed using:

1. Original Product price
2. Original transaction amount
3. Original currency
4. Gateway transaction record
5. Order invoice
6. Payment date

Retain payment documentation for accounting purposes.

Appointment Currency

41.62 Paid Appointment Currency

Paid appointments use the account’s currency and payment configuration.

Before allowing paid booking:

1. Set the correct account Currency.
2. Set appointment prices.
3. Configure at least one compatible Payment Method.
4. Test the booking form.
5. Confirm the gateway receives the expected currency.
6. Confirm the appointment is recorded after payment.

41.63 Appointment Service Prices

When appointments are priced by Service, review every Service’s amount.

A correct account Currency does not correct an incorrect Service amount.

Example:

The public visitor should see and pay:

Currency and Payment-Gateway Compatibility

41.64 Currency Selection Does Not Guarantee Gateway Support

A currency can exist in Book but still be unsupported by a selected payment gateway.

The payment workflow contains explicit unsupported-currency handling for gateways including:

Confirm gateway support before publishing paid Products or Appointments.

41.65 Gateway-Specific Currency Requirements

Some programmed integrations contain strict currency conditions.

Examples found in the customer payment workflow include:

Other gateways accept a defined list of currencies rather than every available currency.

Gateway requirements can also change outside the Book system, so the merchant should confirm supported currencies in their payment-provider account.

41.66 Currency Compatibility Test

Use this test:

1. Select the account Currency.
2. Configure one Payment Method.
3. Create a low-priced test Product or Appointment.
4. Open the public VCard while signed out.
5. Begin checkout.
6. Confirm the displayed Currency.
7. Confirm the gateway checkout Currency.
8. Complete the test payment.
9. Confirm the amount in the merchant dashboard.
10. Confirm the order or appointment in Book.
11. Refund or reconcile the test according to business policy.

Currency Troubleshooting

41.67 Currency Selector Is Empty

Possible causes include:

1. No currencies are available.
2. The page did not load.
3. The customer is operating through a restricted organization account.
4. The currency list was not configured.
5. A browser script failed.

Refresh the page and contact the platform administrator when the list remains empty.

41.68 Organization User Is Asked to Contact the Administrator

The interface includes an organization-user message instructing the user to contact their organization administrator to add Currency in Settings.

This means account-level currency management may be controlled by the organization owner rather than every assigned user.

41.69 Wrong Symbol Appears

Check:

1. Account default Currency.
2. Product-specific Currency.
3. Currency icon assigned to the selected code.
4. Cached public page.
5. Currency Position.
6. Whether the Product was duplicated from another VCard.

41.70 Correct Symbol but Wrong Amount

The Currency setting does not perform automatic conversion.

Edit the Product or appointment amount manually.

41.71 Product Says Currency Is Required

1. Edit the Product.
2. Confirm that a Price is entered.
3. Select a Currency.
4. Save.
5. Reopen the Product.
6. Confirm the Currency remained selected.

41.72 Gateway Says Currency Is Unsupported

1. Record the selected Currency code.
2. Record the selected gateway.
3. Confirm the gateway’s supported currencies.
4. Change to a compatible gateway or Currency.
5. Recalculate the Price when changing Currency.
6. Save the settings.
7. test checkout again.

Do not repeatedly submit the same unsupported transaction.

41.73 Decimal Values Display Incorrectly

Review:

1. Hide Decimal Values
2. Default Currency Format
3. Product Price
4. Browser cache
5. Public template
6. Checkout total
7. Invoice amount

Confirm both display and actual charge.

Part Three: Payment Methods

41.74 Understanding Payment Configuration

Payment Configuration stores the account’s merchant credentials and determines which payment choices can be offered through applicable VCards.

Payment methods can be used for operations such as:

The exact gateways shown depend on the installed integrations and account configuration.

41.75 Opening Payment Configuration

To open Payment Configuration:

1. Sign in to the primary customer account.
2. Select Settings.
3. Open Payment Configuration.
4. Review the available gateways.
5. Select the gateway to configure.
6. Enter the required credentials.
7. Choose the correct operating mode where applicable.
8. enable the configuration where required.
9. Save.

The customer Settings submenu contains a dedicated Payment Configuration destination using the payment_method section.

The customer routes save this information through UserSettingController@paymentMethodUpdate.

41.76 Primary Account and Organization Access

Payment credentials should normally be managed by the primary account owner or organization administrator.

An assigned organization user may see a message such as:

Do not share merchant secrets with every organization user merely to bypass this restriction.

Distinguishing Payment Features

41.77 Account Payment Configuration

Account Payment Configuration contains merchant credentials used by programmed checkout functions.

Examples:

41.78 VCard Payment Links

VCard Payment Links are separate public buttons or links created inside an individual VCard.

A Payment Link may direct a visitor to:

1. An external payment page
2. A donation page
3. A hosted invoice
4. A payment profile
5. Another approved URL

Payment Links have their own create, edit, update, and delete routes inside the VCard editor.

A Payment Link does not necessarily use the account’s stored API credentials.

41.79 Platform Billing

Payment made by the account owner to purchase platform services or an NFC Card is separate from customer-facing payment collection.

Platform billing uses payment methods controlled by the platform.

Entering personal merchant credentials in Payment Configuration does not necessarily change how the account owner pays the platform.

41.80 Manual Payment

Manual Payment allows a visitor to follow offline or manually verified payment instructions.

Examples include:

Manual Payment does not provide automatic bank verification unless a separate process has been integrated.

Supported Customer Payment Workflows

41.81 Programmed Product Payment Methods

The Product purchase controller contains customer-facing payment branches for:

The payment choice displayed to a visitor depends on the account’s saved credentials, available integrations, and currency compatibility.

41.82 Programmed Appointment Payment Methods

Paid appointments can also use several account-level gateways, including:

The appointment workflow creates its payment transaction and then records the appointment according to the applicable gateway result.

41.83 A Gateway May Work for One Feature but Not Another

Do not assume that because a gateway appears in Settings it is fully functional in every payment area.

Test it separately for:

1. Products
2. Appointments
3. Other customer checkout flows

A successful Product payment does not prove that Appointment checkout is correctly configured.

Payment Credentials

41.84 Public Key Versus Secret Key

Payment gateways often issue at least two credentials.

Public key, client ID, or application ID

This can identify the merchant in a browser-facing payment process.

Secret key, client secret, access token, or merchant secret

This authorizes secure server-side operations.

Secret credentials must remain private.

41.85 Never Publish Secret Credentials

Do not place a secret credential in:

Anyone who obtains a secret may be able to misuse the merchant integration.

41.86 Test Credentials Versus Live Credentials

Many gateways issue separate credentials for:

Test credentials

Used for controlled testing without normal live settlement.

Live credentials

Used for real customer transactions.

Do not mix:

Every credential and mode must come from the same environment.

41.87 Use This Configuration

Some gateway sections may include Use This Configuration.

Enable it only after:

1. All required credentials are present.
2. Currency compatibility is confirmed.
3. The operating mode is correct.
4. A test has passed.
5. The public payment choice has been reviewed.

General Gateway Setup Procedure

41.88 Preparing a Gateway Account

Before entering credentials:

1. Create or verify the merchant account.
2. Complete required business verification.
3. Add the settlement bank account.
4. Review the gateway’s supported countries.
5. Review supported currencies.
6. Review transaction fees.
7. Review refund procedures.
8. Open the gateway’s developer or API settings.
9. Confirm whether Test or Live credentials are being used.
10. Copy the credentials securely.

41.89 Saving Credentials in Book

1. Open Settings.
2. Select Payment Configuration.
3. Locate the intended gateway.
4. Enter the required key or client ID.
5. Enter the required secret or token.
6. Select Test, Sandbox, Live, or Production mode where shown.
7. Enable the configuration.
8. Select Save.
9. Confirm a success message.
10. Reopen Payment Configuration and verify that the gateway remains enabled.

For security, the interface may not display a saved secret in full after saving.

41.90 Testing After Saving

1. Create a controlled test Product or paid Appointment.
2. Use a low approved amount.
3. Open the VCard in a private browser.
4. Select the payment option.
5. Confirm the gateway name.
6. Confirm the amount and Currency.
7. Complete the transaction.
8. Wait for the return to Book.
9. Confirm the order or appointment.
10. Confirm the transaction in the gateway dashboard.
11. Confirm the notification email.
12. Reconcile the two records.

Configuring Stripe

41.91 Stripe Credentials

The interface includes fields for:

Use matching credentials from the same Stripe environment.

41.92 Stripe Setup Procedure

1. Open the Stripe merchant dashboard.
2. Select Test Mode for initial testing.
3. Retrieve the Publishable Key.
4. Retrieve the Secret Key.
5. Open Book Payment Configuration.
6. Enter the Stripe Key.
7. Enter the Stripe Secret.
8. Save.
9. Test a Product.
10. Test an Appointment.
11. Confirm the payment appears in Stripe.
12. Replace both credentials with Live keys when production is approved.

41.93 Stripe Troubleshooting

Check for:

1. Test and Live key mismatch
2. Copied whitespace
3. Revoked secret
4. Unsupported merchant country
5. Incorrect Currency
6. Incomplete webhook or return handling
7. Browser extensions blocking checkout

Configuring PayPal

41.94 PayPal Credentials

The interface includes:

The Mode must agree with the credentials.

41.95 PayPal Setup Procedure

1. Open the PayPal developer or merchant account.
2. Create or select an application.
3. Choose Sandbox for testing.
4. Copy the Client ID.
5. Copy the Secret.
6. Open Book Payment Configuration.
7. Enter both credentials.
8. Select the matching PayPal Mode.
9. Save.
10. Test with an approved Sandbox buyer account.
11. Confirm the transaction.
12. Move to Live credentials only after testing.

41.96 PayPal Currency Error

When PayPal rejects a Currency:

1. Confirm the Currency code.
2. Confirm that the PayPal merchant account supports it.
3. Change the Product or account Currency where appropriate.
4. Recalculate the amount.
5. Test again.

The application includes a specific message when the Currency is not supported by PayPal.

Configuring Paystack

41.97 Paystack Credentials

The interface includes:

The source also contains an error message instructing the user to check Paystack credentials when the configuration is incorrect.

41.98 Paystack Setup Procedure

1. Open the Paystack merchant dashboard.
2. Choose Test Mode.
3. Copy the public key.
4. Copy the secret key.
5. Open Payment Configuration.
6. Enter the Paystack Key.
7. Enter the Paystack Secret.
8. Copy the callback URL shown by Book.
9. Add that callback URL to the Paystack settings.
10. Save both systems.
11. Complete a controlled test.
12. Confirm that Book receives the payment result.

41.99 Paystack Callback URL

The callback URL tells Paystack where to return the visitor or payment result.

Copy it exactly.

Avoid:

1. Removing part of the URL
2. Adding spaces
3. Using an HTTP address when HTTPS is required
4. Using an administrator URL
5. Entering a different VCard URL
6. Using a staging URL in Live Mode

Configuring Flutterwave

41.100 Flutterwave Credentials

The interface includes:

The Product workflow also validates the Currency against a supported-currency list before creating the Flutterwave payment.

41.101 Flutterwave Setup Procedure

1. Open the Flutterwave merchant dashboard.
2. Choose the appropriate Test environment.
3. Retrieve the public key.
4. Retrieve the secret key.
5. Enter them in Payment Configuration.
6. Save.
7. Test the intended Currency.
8. Complete a Product transaction.
9. Complete an Appointment test.
10. Confirm both transactions in Flutterwave.

Configuring Razorpay

41.102 Razorpay Credentials

The interface includes:

These credentials are used when creating a Razorpay payment session.

41.103 Razorpay Setup Procedure

1. Open Razorpay.
2. Select Test Mode.
3. Generate or retrieve the Key ID.
4. Retrieve the Key Secret.
5. Enter the values in Book.
6. Save.
7. Open a public Product or Appointment.
8. Complete a test transaction.
9. Confirm the Razorpay payment.
10. Confirm the Book record.

Configuring PhonePe

41.104 PhonePe Requirements

The interface contains PhonePe merchant credential terminology, including a Merchant ID.

The programmed Product and Appointment workflows require INR for PhonePe.

41.105 PhonePe Setup Procedure

1. Confirm that the merchant account supports the required integration.
2. Retrieve the required PhonePe credentials.
3. Confirm that the account or item Currency is INR.
4. Enter the credentials in Payment Configuration.
5. Save.
6. Test in the applicable test environment.
7. Confirm the return and transaction record.

Configuring Mercado Pago

41.106 Mercado Pago Credentials

The interface includes:

The payment controller loads these customer settings when creating a Mercado Pago Product checkout.

41.107 Mercado Pago Setup Procedure

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

Treat the Access Token as a secret.

Configuring PayFast

41.108 PayFast Credentials

The interface includes:

The programmed payment workflow requires ZAR for PayFast.

41.109 PayFast Setup Procedure

1. Open the PayFast merchant account.
2. Select the appropriate Sandbox or Live environment.
3. Copy the Merchant ID.
4. Copy the Merchant Key.
5. retrieve or set the Passphrase.
6. Enter all fields in Book.
7. Select the matching PayFast Mode.
8. Confirm that the Currency is ZAR.
9. Save.
10. Complete a controlled test.

Configuring Iyzico

41.110 Iyzico Credentials

The interface includes:

The payment workflow also validates supported Currency before initiating payment.

41.111 Iyzico Setup Procedure

1. Open the Iyzico merchant account.
2. Select Sandbox for testing.
3. Retrieve the API Key.
4. Retrieve the Secret Key.
5. Enter both in Book.
6. Select the matching Iyzico Mode.
7. Save.
8. Test the Currency.
9. Complete a test transaction.
10. Confirm the result in both systems.

Configuring Cashfree

41.112 Cashfree Credentials

The interface includes:

The programmed Product and Appointment workflows require INR.

41.113 Cashfree Setup Procedure

1. Open the Cashfree merchant account.
2. Select Test or Sandbox.
3. Retrieve the App ID.
4. Retrieve the Secret.
5. Enter the credentials in Book.
6. Select the matching Mode.
7. Confirm that the Currency is INR.
8. Save.
9. Test checkout.
10. Confirm the Cashfree session and Book transaction.

Configuring Manual Payment

41.114 Understanding Manual Payment

Manual Payment allows the customer to submit a payment request without an automatically confirmed gateway transaction.

The system can record:

The request remains pending until it is reviewed and verified.

41.115 Creating Clear Manual-Payment Instructions

Manual-payment instructions should include:

Do not publish unnecessary sensitive bank information.

41.116 Manual-Payment Procedure for the Visitor

The visitor generally:

1. Selects Manual Payment.
2. Reviews the instructions.
3. Sends payment through the stated method.
4. Retains the transaction reference.
5. Submits the booking or purchase.
6. Sends proof where required.
7. Waits for verification.

41.117 Verifying Manual Payment

The business should:

1. Locate the pending request.
2. Match the customer.
3. Match the amount.
4. Match the Currency.
5. Match the payment reference.
6. Verify funds directly in the receiving account.
7. Confirm that the payment is not reversed.
8. Update the applicable order or appointment.
9. Notify the customer.

Do not approve a transaction based only on a screenshot.

41.118 Manual Payment Remains Pending

This is expected until authorized staff verify it.

The interface contains customer messaging that a Manual Transaction Request is pending approval.

Enabling Payment on Products

41.119 Product Payment Preparation

Before publishing a paid Product:

1. Create the Product.
2. Enter the correct Price.
3. Select the Currency.
4. Confirm the Product URL and description.
5. Configure at least one Payment Method.
6. Save.
7. Open the public VCard.
8. Select the Product.
9. Begin checkout.
10. Confirm the available payment choices.

41.120 Product Checkout Record

A successful Product payment should be matched across:

Do not rely on only one record for fulfillment.

Enabling Payment on Appointments

41.121 Appointment Payment Preparation

Before requiring payment:

1. Configure Appointment availability.
2. Set appointment or Service amounts.
3. Select the account Currency.
4. Configure a compatible gateway.
5. Enable the paid-booking option.
6. Save.
7. Test the complete public booking process.

41.122 Appointment Is Created but Payment Is Pending

Possible causes include:

1. Manual Payment was selected.
2. The gateway return did not complete.
3. Verification is delayed.
4. The visitor closed the browser.
5. Payment failed after the booking record was started.
6. The callback is misconfigured.

Verify the gateway before confirming the appointment as paid.

Payment Statuses

41.123 Pending

Pending means the payment has not been fully verified.

Do not fulfill a paid Product or treat a paid Appointment as confirmed solely because a pending record exists.

41.124 Successful or Paid

Successful or Paid indicates that the system recorded a successful result.

Also confirm the payment in the merchant gateway before delivering high-value products or services.

41.125 Failed

Failed means the payment could not be completed or verified.

Possible reasons include:

1. Declined payment
2. Invalid credentials
3. Unsupported Currency
4. Gateway error
5. Authentication failure
6. Expired session
7. Callback verification failure

41.126 Cancelled

Cancelled can occur when:

1. The customer cancels checkout.
2. The browser is closed.
3. The gateway session expires.
4. The customer returns without payment.
5. The gateway reports cancellation.

A cancelled payment should not be fulfilled.

Refunds and Reversals

41.127 Processing Refunds

Refunds are normally initiated through the applicable merchant gateway unless a dedicated Book refund action is available for that transaction.

Recommended procedure:

1. Locate the Book order or appointment.
2. Locate the gateway transaction.
3. Confirm the customer and amount.
4. Review the refund policy.
5. Initiate the refund through the gateway.
6. Retain the refund reference.
7. Update the Book record where appropriate.
8. Notify the customer.
9. Reconcile accounting records.

41.128 Manual-Payment Refunds

A manual payment must normally be refunded through the original offline payment channel.

Record:

41.129 Do Not Change Currency to Simulate a Refund

Changing the account or Product Currency does not reverse a transaction.

A refund must be tied to the original payment record.

Payment Security

41.130 Restrict Credential Access

Only authorized account owners or organization administrators should manage Payment Configuration.

Do not give access merely because a staff member needs to view orders.

41.131 Use Two-Factor Authentication

Enable two-factor authentication on:

1. Book account
2. Payment-gateway account
3. Business email account
4. Banking account where available

This helps protect both credentials and settlement information.

41.132 Rotate Compromised Credentials

When a secret may have been exposed:

1. Disable or rotate it in the gateway dashboard.
2. Generate a replacement.
3. Update Payment Configuration.
4. Save.
5. Test the new credentials.
6. Review recent transactions.
7. Remove the exposed secret from messages, files, or repositories.
8. Document the incident.

41.133 Do Not Send Secrets by Email

When technical support needs to verify configuration:

1. Send screenshots with secrets hidden.
2. Identify only the last few characters where useful.
3. Use an approved secure credential-sharing method.
4. Rotate the secret after emergency sharing where necessary.

41.134 Review Gateway Users

Payment gateways may allow several team accounts.

Give each staff member an individual login with the minimum required permissions.

Avoid sharing one merchant password.

41.135 Protect Customer Payment Information

Book should not be used to collect raw card numbers through an ordinary text field, Inquiry, Product description, or Appointment remark.

Customers should enter sensitive payment information only through the authorized gateway’s secure checkout.

Payment Troubleshooting

41.136 Payment Configuration Is Missing

Confirm:

1. The primary customer account is being used.
2. Settings loaded completely.
3. Payment Configuration is selected.
4. The organization administrator has access.
5. The relevant gateway integration is installed.

The customer settings submenu identifies Payment Configuration as a dedicated section.

41.137 “Please Add Payment Credentials”

This message means the selected payment method lacks required account credentials.

1. Open Payment Configuration.
2. Locate the gateway.
3. Enter every required field.
4. Confirm the correct mode.
5. Save.
6. Test again.

41.138 Organization User Cannot Add Credentials

The organization administrator must configure the gateway.

Do not send the secret to the assigned user through an ordinary chat message.

41.139 Credentials Are Rejected

Check:

1. Leading or trailing spaces
2. Test and Live mismatch
3. Copied incomplete secret
4. Revoked API key
5. Wrong merchant account
6. Wrong Mode
7. Expired application credentials
8. Incorrect callback
9. Gateway account not activated

41.140 Payment Option Does Not Appear Publicly

Confirm:

1. The gateway configuration is enabled.
2. Required fields are present.
3. Currency is selected.
4. Product or Appointment has a Price.
5. The public VCard is active.
6. The applicable paid feature is enabled.
7. Browser cache is cleared.
8. The gateway is supported by that checkout flow.

41.141 Gateway Opens but Shows the Wrong Amount

Review:

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

Stop checkout until the amount is correct.

41.142 Gateway Opens in the Wrong Currency

Check:

1. Product-specific Currency.
2. Account default Currency.
3. Gateway-supported Currency.
4. Existing checkout session.
5. Whether the Product was edited after checkout began.

Create a new test session after saving corrections.

41.143 Test Credentials Are Charging Real Money

Stop using the gateway immediately.

Confirm:

1. Mode selection
2. Key prefix
3. Merchant environment
4. Whether Live credentials were accidentally pasted
5. Whether the gateway account treats the transaction as Live

41.144 Live Credentials Produce a Test Checkout

Confirm that:

1. Live Mode is selected.
2. Both credentials are Live.
3. A test callback URL is not being used.
4. The merchant account is activated.
5. The public VCard is not on a staging installation.

41.145 Payment Succeeds but Book Shows Pending

1. Do not charge the customer again.
2. Record the gateway transaction ID.
3. Confirm the payment in the merchant dashboard.
4. Refresh Book.
5. Review callback or webhook configuration.
6. Confirm the return URL.
7. Contact technical support with the Book record and gateway reference.
8. Update fulfillment only after verification.

41.146 Book Shows Paid but Gateway Has No Payment

Treat the transaction as unverified.

Check:

1. Test versus Live dashboard
2. Transaction ID
3. Correct merchant account
4. Manual-payment status
5. Whether the Book record was updated manually
6. Whether the gateway payment was reversed

41.147 Customer Was Charged Twice

1. Locate both gateway transactions.
2. Locate both Book records.
3. Compare timestamps and amounts.
4. Determine whether two orders were created.
5. Stop fulfillment of the duplicate.
6. Refund the duplicate according to policy.
7. Retain both references.
8. Investigate repeated form submission.

41.148 Customer Closed the Browser After Payment

A gateway callback may still update the transaction.

Before requesting another payment:

1. Check the gateway.
2. Check the Book order.
3. Refresh the dashboard.
4. Search by customer email.
5. Wait for delayed verification.
6. Contact support where records disagree.

41.149 Callback URL Error

Confirm:

1. Exact HTTPS URL
2. Correct domain
3. Correct environment
4. No spaces
5. No missing path
6. No obsolete staging domain
7. Gateway allows the URL
8. SSL certificate is valid

41.150 Payment Page Is Blank

Try:

1. Another browser
2. Private browsing
3. Disabling blocking extensions
4. Confirming JavaScript is enabled
5. Checking the gateway service
6. Confirming credentials
7. Confirming Currency
8. Starting a new checkout session

41.151 Manual Payment Is Not Available

Confirm that:

1. Manual-payment configuration is enabled.
2. Instructions have been provided.
3. The applicable Product or Appointment allows it.
4. The public page is current.
5. The account administrator saved the setting.

41.152 Manual Payment Was Approved Incorrectly

1. Recheck the receiving account.
2. Contact the customer.
3. Pause fulfillment.
4. Correct the Book status.
5. Document who approved it.
6. review the verification procedure.
7. Require direct fund verification for future requests.

Combined Operational Workflow

41.153 Recommended Setup Order

Use this order when preparing the account:

41.154 Why This Order Matters

Storage should be reviewed before adding large Product catalogs.

Currency should be finalized before gateway testing.

Payment Methods should be verified before publishing paid Products or Appointments.

This prevents:

1. Failed uploads
2. Incorrect symbols
3. Unsupported Currency errors
4. Incorrect charges
5. Unpaid fulfillment
6. Confusing public checkout

Final Storage Checklist

41.155 Storage Review Checklist

Confirm that:

1. Storage opens from the main menu.
2. Used Storage has been reviewed.
3. Unused Storage has been reviewed.
4. The assigned Storage Limit is understood.
5. Oversized images have been identified.
6. Duplicate Products have been reviewed.
7. Galleries have been reviewed.
8. Old Banners have been reviewed.
9. WhatsApp Store media has been reviewed.
10. Important originals are backed up.
11. Media is deleted through its original feature.
12. Public VCards are tested after cleanup.
13. Confidential files are not stored as public media.

Final Currency Checklist

41.156 Currency Configuration Checklist

Confirm that:

1. The correct default Currency is selected.
2. The Currency code is correct.
3. The Currency icon is correct.
4. Currency Position is correct.
5. Decimal display is correct.
6. Product-specific currencies are reviewed.
7. Product Prices match their selected currencies.
8. Appointment amounts are correct.
9. Currency changes were not mistaken for conversions.
10. Historical transactions remain documented.
11. The selected gateway supports the Currency.
12. Public Products and Appointments were tested.

Final Payment Checklist

41.157 Payment Configuration Checklist

Confirm that:

1. The primary account owner configured the gateway.
2. The merchant account is verified.
3. Settlement details are complete.
4. The correct gateway was selected.
5. Public and secret credentials match.
6. Test or Live Mode is correct.
7. Callback URLs are correct.
8. Currency compatibility was verified.
9. The configuration is enabled.
10. Product checkout was tested.
11. Appointment checkout was tested.
12. Gateway and Book records match.
13. Manual-payment instructions are clear.
14. Secret credentials are protected.
15. Refund procedures are documented.
16. Staff know how to identify Pending, Paid, Failed, and Cancelled payments.

Chapter Completion

At the end of this chapter, the user should understand how to open and interpret Storage, monitor Used and Unused Storage, identify media that consumes account space, optimize and safely remove files, set the account’s default Currency, assign Product-specific currencies, control Currency Position and decimal display, avoid treating a currency change as an exchange-rate conversion, configure customer-facing payment gateways, protect merchant credentials, manage Manual Payments, test Product and Appointment checkout, reconcile transactions, and troubleshoot storage, currency, callback, credential, and payment-status problems.