Reserve Requests

Menu path: Admin -> Reserve Request

This section is used when customers ask you to prepare more reserve for a currency.

It is useful when a customer wants to exchange into one currency, but your current reserve is too low.

Main pages

• Overview Dashboard
• Reserve Request List
• Add Reserve Request
• Request Pending
• Reserve Request Details
• Update Reserve Request

Where reserve requests come from

Reserve requests can enter the system in these ways:

• a visitor or customer submits a reserve request from the public rates page
• a logged-in customer later sees their own reserve requests in the customer area
• an admin creates a reserve request manually from the admin panel

What you can do

• monitor demand for low-reserve currencies
• see which requests still need action
• create a request manually for a customer or visitor
• review request details and customer details
• change the request status
• write a status reason
• check request history
• review system information for public requests

Overview Dashboard

The Overview Dashboard gives a quick summary before you open the full list.

It shows sections such as:

• Total Requests: all reserve requests in the system
• Pending Queue: requests still waiting for action
• Confirmed: requests already approved
• Last 24 Hours: new reserve requests received recently
• Top Requested Currencies: currencies that customers request most often
• Status & Customer Mix: pending, confirmed, guest, and logged-in customer totals
• Latest Reserve Requests: newest requests with reference, customer, currency, amount, status, and date

Use this page when:

• you want to see demand trends quickly
• you want to know whether the pending queue is growing
• you want to know which currencies need reserve planning first

Reserve Request List page

This is the full list of reserve requests.

It shows columns such as:

• Date
• Reference
• Customer
• Email
• Currency
• Amount
• Status
• Action

What the columns mean

• Date: when the request was created
• Reference: the request number
• Customer: customer name, with a link when the request is linked to a real customer account
• Email: contact email for the request
• Currency: requested currency title and code
• Amount: requested amount in that currency
• Status: current request state
• Action: edit, show, or delete options

List page actions

From the list page, admins can usually:

• search requests
• filter by table search
• export the table
• print the table
• reload the table
• open one request
• edit one request
• delete one request

Request Pending page

Request Pending is the working queue for reserve requests that still need attention.

This page shows only requests with Pending status.

Use this page when:

• you want to process today’s open requests first
• your team wants one clean queue instead of the full history
• you want to avoid missing older pending requests inside the full list

Add Reserve Request and Update Reserve Request

The create and update pages use the same main form.

This form is for editing the basic request information.

Field guide

Field	What it means	Validation or good input
Customer	Optional linked customer account	Search and select a real customer if the request belongs to a registered user
Customer Name	Display name for the request	Required. Use the customer’s real full name
Customer Email	Contact email for request updates	Required. Must be a valid email address
Customer Phone	Contact phone number	Fill a real number the customer can answer
Currency	Currency the customer wants you to prepare reserve for	Required. Choose the exact currency carefully
Amount	Requested reserve amount	Required. Use a number greater than 0 for real requests
Status	Current request stage on this form	Required. On this page you can use Pending or Confirmed
Comment	Short note about the request	Use a clear note, request purpose, or extra instruction

Customer field

The Customer field uses search.

When you select a customer:

• the form fills the customer name automatically
• the form fills the customer email automatically
• the form fills the customer phone automatically

This saves time and helps prevent typing mistakes.

If the request does not belong to a registered customer:

• leave Customer empty
• type the customer name manually
• type the email manually
• type the phone manually

Currency field

Choose the exact currency the customer needs.

This matters because:

• the request will appear under that currency in reports and dashboards
• the amount is shown together with the selected currency code
• admins may open the linked currency page from the request details screen

Amount field

Use the amount the customer really wants to exchange into.

Good examples:

• 100
• 250.50
• 1000

Avoid:

• leaving it as 0
• entering letters instead of numbers
• using the wrong currency with the right amount

Comment field

Use this field for short, helpful notes such as:

• why the customer needs this reserve
• how urgent it is
• whether the customer already contacted support
• any special handling note

Keep the comment short and clear.

Status guide

Reserve requests can use these statuses:

Status	Meaning	When to use it
Pending	Request is received and still waiting for review	Use when the team has not decided yet
Confirmed	Request is approved and the reserve need has been accepted	Use when you are ready to treat the request as handled
Declined	Request is not approved	Use when you cannot provide the requested reserve

Important status note

The Add Reserve Request and Update Reserve Request pages do not show every final status.

On those pages, the main form uses:

• Pending
• Confirmed

If you need to mark a request as Declined, use the Update Status form inside the request details page.

Reserve Request Details page

Open one request from the list when you need the full information.

This page has three main tabs:

• Summary
• History
• System Info

Summary tab

The Summary tab is the main working page for one request.

It contains these sections:

• Customer
• Invoice
• Request Information
• Update Status

Customer card

This area shows:

• customer name
• email
• phone
• verification icon when the request is linked to a registered customer
• referred-by information when available

If the request belongs to a real customer account, the customer name links to the customer profile.

Invoice card

This area shows:

• Reference ID
• Status
• Date Added
• Last Update

Use it when:

• the customer asks for the request number
• you need to confirm the current status quickly
• you need to see when the request was last changed

Request Information card

This area shows:

• Currency
• Amount
• Comment

The amount field also includes a quick copy icon.

That helps when you need to copy the amount into a message or internal note.

Update Status form

This form is inside the request details page.

Use this form for final review actions.

Field guide

Field	What it means	Validation or good input
Status	New status for the request	Required. Choose Pending, Confirmed, or Declined
Reason	Explanation for this status change	Write a clear reason, especially when you decline a request

When to use each status here

• choose Pending if the request still needs follow-up
• choose Confirmed if the reserve request is accepted
• choose Declined if the request cannot be fulfilled

Reason field

The Reason field is very important.

Use it to explain:

• why the request is still pending
• why the request was approved
• why the request was declined

Good examples:

• We are arranging reserve for this currency today.
• Reserve has been prepared and the request is approved.
• This currency is currently unavailable for reserve increase.

History tab

The History tab shows the request status timeline.

It normally includes:

• Date Added
• Comment
• Order Status
• Processor

Use this tab when:

• the customer asks what happened earlier
• another admin already worked on the request
• you need to review the previous status flow before changing it again

System Info tab

The System Info tab can show request environment details such as:

• IP address
• browser or device information
• request domain
• location-related IP information when available

Important note:

• public reserve requests usually contain this information
• manually created admin requests may not show system information

How public reserve request submission works

The public reserve request form is usually opened from the rates page.

The normal flow works like this:

1. The user opens the rates page
2. The user clicks the reserve request button for one currency
3. The modal opens with that currency already selected
4. The user fills the contact form
5. The request is submitted
6. The system saves the request as Pending
7. The request appears in Admin -> Reserve Request
8. If notifications are enabled, the customer and admin can receive updates

If the user is logged in:

• the reserve request can also be linked to that customer account
• the customer can later review it from the customer reserve request page

Public reserve request form details

The customer-facing form includes these fields:

Field	What it means	Validation or good input
Name	Request sender name	Required. Use letters and spaces only
Email	Contact email	Required. Must be a valid email address
Phone	Contact number	Optional, but strongly recommended
Amount	Requested amount	Required. Must be a number
Comment	Extra details about the request	Optional. Keep it short and clear
Currency	Requested currency	Filled by the reserve request button the user clicked

Public form validation notes

• Name should contain only letters and spaces
• Name should not be too short
• Email must be a valid email address
• Amount must be numeric
• Comment should stay short

Notifications and related settings

Reserve requests can send notifications when the feature is configured.

Check these settings pages:

• Notification Settings
• SMTP Configuration
• Telegram Configuration

Common notification uses:

• email update when a request is submitted
• email update when the status changes
• Telegram alert when reserve request notifications are enabled

Common mistakes

• selecting the wrong currency
• entering the amount without checking the currency code
• leaving the customer field blank when the request belongs to a registered customer
• selecting a customer and then changing the contact fields to incorrect values
• expecting Declined to appear on the main create form
• changing the status without writing a clear reason
• forgetting to enable reserve request notifications in settings

If admin save fails

Check these points first:

• Customer Email is a valid email address
• Currency is selected
• Amount is numeric
• Amount is not negative
• Status is selected
• if you selected a customer, it is a real customer from the search field
• long comments are shortened to a reasonable length

If public submission fails

Check these points first:

• Name contains letters and spaces only
• Name is not too short
• Email is valid
• Amount is numeric
• the selected currency is still available

Best practice

• use Request Pending as the daily work queue
• select the linked customer whenever possible
• write short, useful comments and reasons
• review Currency before confirming large requests
• keep reserve request email and Telegram notifications configured
• use the details page for final status decisions and history review

Related pages

• Currency
• Customer
• Notification Settings
• SMTP Configuration
• Telegram Configuration
• Dashboard