Question 1

Does Bricspay move real money?

Accepted Answer

No. Bricspay is a test environment. Accounts and currencies are simulated. It does not initiate real transfers, hold real funds, create or change real balances, reserve funds, or settle payments. Any quoted rate, fee, balance, reservation, or outcome is a test value only.

Question 2

What does each request status mean?

Accepted Answer

These labels are shown in workflow order, not as a guaranteed path for every request:
1. Request submitted — the test request was recorded.
2. Pending review — review is pending; the request may be held or rejected.
3. Message sent — a payment message was recorded as sent. This is not settlement.
4. Counterparty accepted — acceptance was recorded as a separate workflow decision.
5. Test settlement confirmed — the simulator recorded a test settlement result; no funds moved.
6. Beneficiary credited — a separate simulated beneficiary-credit event was recorded; no real balance changed.
7. Rejected — the request was declined during review or by the counterparty. This is a separate outcome from a return.
8. Returned — a test refund/return outcome, recorded separately after a simulated settlement or beneficiary-credit event.
A request can stop at review, be held, or be rejected. It does not necessarily reach settlement or beneficiary credit.

Question 3

Are rates, fees, balances, or results real?

Accepted Answer

No. Any rate, fee, balance, reservation, liquidity figure, or result shown in the test environment is simulated or a sample value. It is not a live quote, a real account balance, a commitment to transfer funds, or evidence that a payment settled.

Question 4

Which compliance checks have been completed?

Accepted Answer

None have been run or completed as real compliance screening or review in this test environment. KYC/KYB, beneficial-ownership checks, AML/CFT controls, counterparty screening, transaction limits, and source-of-funds review are planned controls. In the designed workflow, a failed, incomplete, or unavailable critical check holds progression for review; it does not release a payment.

Question 5

What does auditability mean here?

Accepted Answer

The workflow is designed to trace events, decisions, approvals, status changes, and references to evidence. Identity documents and invoices stay off public blockchains. Current dashboard event and audit views are placeholders; they do not show connected live history. A message, event, or ledger record is not proof of final settlement.

Question 6

Does sending a message mean a payment has settled?

Accepted Answer

No. A sent message records communication. Counterparty acceptance records a separate workflow decision. Neither is settlement, and neither proves that funds moved. Test settlement confirmation and beneficiary credit are separate simulated events; this environment has no operational settlement.

Question 7

Is Bricspay connected to banks or settlement systems?

Accepted Answer

This test environment makes no claim of an active connection to a bank, correspondent bank, RTGS, wholesale CBDC, or other settlement system. It does not perform operational settlement. Bricspay does not claim a license, regulatory approval, or official BRICS affiliation. Any future integration is conditional on real counterparties, agreements, applicable approvals, and technical activation.