WEBVTT

00:00:01.300 --> 00:00:05.169
We are ready to follow one Paper purchase. In the demonstration, the

00:00:05.169 --> 00:00:09.038
selected market, quantity, and account have already been checked. If you are

00:00:09.038 --> 00:00:12.907
watching only, follow the request with us. If you are practicing in

00:00:12.907 --> 00:00:16.776
your own Paper account, use the controls and available balance you actually

00:00:16.776 --> 00:00:20.000
have. Do not change to Live to match a demonstration.

00:00:20.500 --> 00:00:24.410
On Confirm Purchase, select Yes, Buy Now once. That sends the requested

00:00:24.410 --> 00:00:28.320
asset quantity for validation and handling. The app checks the request and

00:00:28.320 --> 00:00:32.230
attempts the purchase. The time between clicking and receiving a response is

00:00:32.230 --> 00:00:36.139
not evidence that an order failed. A quiet screen can simply mean

00:00:36.139 --> 00:00:40.049
that the work has not finished or that the response has not

00:00:40.049 --> 00:00:40.375
arrived.

00:00:40.875 --> 00:00:44.653
The current buy form does not show a dedicated, reliable progress stage

00:00:44.653 --> 00:00:48.431
for every request, and its submit button is not a promise of

00:00:48.431 --> 00:00:52.209
duplicate-click protection. Keep your hands off the button after the first click.

00:00:52.209 --> 00:00:55.987
Do not double-click, press it again in another tab, or change the

00:00:55.987 --> 00:00:59.450
amount and submit a replacement while the first result is unknown.

00:00:59.950 --> 00:01:03.598
Our animation will show a request traveling to the service and a

00:01:03.598 --> 00:01:07.245
response returning. That is an explanation of the process, not an extra

00:01:07.245 --> 00:01:10.893
status panel you must find in the app. In an actual session,

00:01:10.893 --> 00:01:14.540
use the visible response and the account records. A teaching animation should

00:01:14.540 --> 00:01:18.188
help you understand what to check, not create confidence that a hidden

00:01:18.188 --> 00:01:19.100
step has succeeded.

00:01:19.600 --> 00:01:23.549
On the current successful-response path, the purchase form closes and the app

00:01:23.549 --> 00:01:27.498
asks its account views to refresh. That is your cue to inspect

00:01:27.498 --> 00:01:31.447
the result. It is not a reason to assume every requested unit

00:01:31.447 --> 00:01:35.396
is now owned. We still need to find the resulting position and

00:01:35.396 --> 00:01:37.700
recorded activity in the same Paper context.

00:01:38.200 --> 00:01:42.258
If an error appears, read and note it promptly. The buy form's

00:01:42.258 --> 00:01:46.316
error message can disappear after a short time. Capture the relevant wording

00:01:46.316 --> 00:01:50.375
and the time of the attempt without sharing private account details. A

00:01:50.375 --> 00:01:54.433
message about validation, funds, or access points to a different next step

00:01:54.433 --> 00:01:56.800
from a connection that simply stopped responding.

00:01:57.300 --> 00:02:01.448
If the response remains uncertain, stop making new requests. Check Portfolio and

00:02:01.448 --> 00:02:05.597
Transactions for the same pair and approximate time. A missing update might

00:02:05.597 --> 00:02:09.745
be a delay; a closed form might follow a response whose details

00:02:09.745 --> 00:02:13.893
you have not yet examined. Neither observation alone is a complete answer.

00:02:13.893 --> 00:02:17.350
We will work through recovery carefully on the final page.

00:02:17.850 --> 00:02:21.900
For now, the successful pattern is simple: review once, submit once, wait,

00:02:21.900 --> 00:02:25.950
then verify. Record the quantity you requested so you have something precise

00:02:25.950 --> 00:02:30.000
to compare with the outcome. That small note turns the next screen

00:02:30.000 --> 00:02:34.050
from a collection of changing numbers into a question you can answer:

00:02:34.050 --> 00:02:36.075
what changed because of this request?