In this guide
Approval Plus Mortgage
Practical guides

Keep separate funding requests matched to the right transfers

Two open payment windows are two separate instructions. A small request log helps you avoid reporting a transfer against the wrong amount or network.

Start with the requests already in Deposits

Open Deposits before creating another funding request. The Payment windows list shows existing amounts, asset and network information, dates and statuses, with an Open action for each request. Open the relevant entry and read its details. A browser tab is only a way to view a request; it is not a reliable name for the payment, especially after tabs have been duplicated or reordered.

The account currently allows up to three active payment windows. If you reach that limit, return to an existing request instead of repeatedly trying to create another one. This is a limit on simultaneous open windows, not permission to apply one transfer to three requests. Each request has its own instructions and fifteen-minute deadline.

Sources & further reading: [1]

Give each request its own short record

For each open request, record the request reference shown in its details, creation time, asset, network, quoted amount and deadline. Keep the receiving address and any required memo with that same record. A label such as “first request” becomes ambiguous when a colleague or a second browser session is involved; the account reference remains the useful identifier.

Suppose you opened one USD 50 request and another USD 100 request. Keep two rows, then add the actual transaction hash beside the row you paid. If both requests are for USD 50, their equal amounts still do not make them interchangeable. Use the request reference, time and asset-network pair to distinguish them. Do not assume a receiving address by itself uniquely identifies your intended request.

Sources & further reading: [1]

Compare the request again immediately before sending

Finish one transfer deliberately before moving to the next. Reopen its instructions, compare the selected token and network, and check the entire receiving address and any memo against the sending screen. Send the amount instructed for that request. The account quote separates what you send from its top-up fee and expected account credit; a sending-wallet charge is a separate check.

The minimum funding amount is USD 10. Under the current fees, a request below USD 300 has a 1% top-up fee, while a request of USD 300 or more has none. Treat the threshold per request: two USD 150 requests do not become one USD 300 request for fee calculation. Use the displayed quote rather than adding separate windows together to estimate their fee.

Sources & further reading: [1] [2]

Report the transfer on the matching request

After sending, obtain the complete transaction hash or ID from the sending wallet or service. On the correct open request, enter it in the already-paid form and use I have paid — submit for review. Check the amount and network at the top of that same dialog before submitting. Keep the reported hash in your own request log so you can later compare the account record with the transfer.

Reporting a hash places the payment under review; it is not an immediate credit confirmation. Do not submit one transfer as evidence for two different requests. If you attached the wrong hash, contact support with both request references and explain which transfer belongs to which request. The current form does not let you overwrite a previously reported hash with a different one.

Sources & further reading: [1] [3]

Resolve each window according to what actually happened

Reopening a request or refreshing its status does not restart its fifteen-minute window. If one request expires unpaid, do not mark it as paid to clear the list. If you already sent its transfer but the window ended before verification, use that request’s refund form with the original transaction evidence and a suitable same-network refund address. Keep this separate from any other request that remains open or has already been credited.

For a support message, provide a compact mapping: request reference, amount, asset-network pair, transfer hash if sent, and the status you observed. State the time and timezone of your observation. Do not include the private Approval Plus access seed, wallet recovery phrase, full card number or security code. A clear two-row explanation is more useful than several screenshots with no indication of which payment each image describes.

Sources & further reading: [1] [3]

Your questions, answered

Does refreshing a request create a new payment window?

No. Reopening or refreshing the same request keeps its existing deadline. Use its reference and status to follow that request rather than treating a new browser view as a new payment.

Can I use one transfer hash for two requests?

Do not report one transfer as payment for two requests. Match the actual transfer to its intended request and ask support to correct a mistaken association.

Do two USD 150 requests qualify for the USD 300 fee threshold?

No. The current threshold applies to each request separately. Read each request’s quoted fee and net credit before sending.

Sources & further reading

  1. Approval Plus: account and funding help ↗Checked Nov 16, 2026
  2. Approval Plus: current funding fees ↗Checked Nov 16, 2026
  3. Approval Plus: contact support ↗Checked Nov 16, 2026
APPROVAL PLUS

Your next step

Account, funding and card guidance in your language.

APPROVAL PLUS

Need a hand?

Our support team can help with your account, funding and card questions.

support@approvalplusmortgage.com