Shortmill
Autosaved just now
User Menu
Stage 01 / 07
Script
Landscape (16:9)
~5 Minutes
Working Brief
Generate
Use my script
Generate script
40 Scenes
Regenerate
01
You walk into a coffee shop in the United States and order a five-dollar coffee. You tap your card. The terminal beeps. The barista hands you the cup, and you leave.
13.6s
02
But freeze that moment. The screen said approved. Had the money actually reached the coffee shop's bank account?
7.9s
03
To find out, follow this purchase beyond the counter.
4.0s
04
There are two questions underneath that little screen. Can the payment proceed? And how does the shop get paid? The first answer doesn't complete the second job.
11.9s
05
We'll follow a physical debit card, with approval from your bank and separate financial processing afterward.
7.0s
06
Other routes exist. And one provider can perform several jobs. Our map separates the functions, not necessarily the companies.
8.4s
07
At the tap, the card and terminal communicate payment data, including security information for this transaction.
7.0s
08
The terminal sends an approval request. In everyday language: this card, this shop, five dollars. Can the purchase proceed?
8.4s
09
First, the request enters the shop's payment services. A processor handles transaction messages. The acquiring side supports the shop's card acceptance.
9.2s
10
These services connect the counter to the wider payment system. Some providers combine both roles.
6.6s
11
The card network carries the request from the merchant's side to the bank that issued your card.
7.5s
12
Think of the network here as the bridge between the shop's financial side and yours. It also has jobs later in the story.
10.1s
13
Your bank examines the request. Is the card valid? Can the account cover the purchase? Are there fraud concerns?
8.4s
14
These are example checks, not a complete checklist. For our coffee purchase, the bank sends back an approval.
7.9s
15
That answer returns through the network and the shop's payment services. The terminal displays approved.
6.6s
16
This is authorization: permission for the payment to proceed. It isn't confirmation that the shop's bank account has received the money.
9.2s
17
But perhaps your banking app already shows less money available.
4.4s
18
Authorization can place a hold on the five dollars, reducing what you can spend. A reservation on your side is still different from money arriving in the shop's account.
12.8s
19
Back at the counter, you have your coffee. From your perspective, checkout is finished.
6.2s
20
Now the payment system must process the completed sale. Keep the same cup in view: we're still following that one purchase.
9.2s
21
The shop's system submits the authorized payment for processing. This is capture, and it can happen automatically during checkout.
8.4s
22
Authorization asks for permission. Capture submits the sale. We separate them to explain their jobs, not to imply a long pause.
9.2s
23
Next, clearing exchanges the sale's financial details between the acquiring and issuing sides through the network.
7.0s
24
The coffee purchase can be recorded against the right account, and the financial parties reconcile what is owed. We're following a record, not the shop's payout.
11.4s
25
The record still identifies our five-dollar coffee.
3.1s
26
But recording an obligation and moving funds to meet it are different jobs. That's the next layer: settlement.
7.9s
27
Under the network's settlement arrangements, funds are exchanged between the issuing and acquiring sides.
6.2s
28
The network facilitates this process. The funds path on our map represents settlement between those financial sides, not five dollars deposited into a network wallet.
11.0s
29
Your coffee needn't create its own separate five-dollar bank transfer.
4.4s
30
Settlement can combine many transactions into net amounts owed. The coffee remains an individual sale in the records, while contributing to a larger financial position.
11.0s
31
Even funds received by the acquiring or payment-provider side aren't automatically funds in the shop's bank account.
7.5s
32
Merchant payout credits that account under the shop's arrangement. It can combine sales, with fees and other adjustments affecting the amount.
9.2s
33
Our example follows a payout arrangement that waits for the provider to receive funds. Other arrangements advance money to merchants. There is no universal waiting time.
11.4s
34
Merchant fees can include multiple components. There isn't one standard slice taken from every coffee.
6.6s
35
Replay the purchase. The tap starts communication. Authorization returns a decision. Capture submits the sale. Clearing exchanges financial records. Settlement meets financial obligations. Payout reaches the shop.
11.9s
36
One coffee. Different jobs, connected underneath the counter.
3.5s
37
Each participant contributes a service: accepting the payment, processing messages, checking the account, or coordinating records and settlement.
7.9s
38
The screen shows the answer needed at checkout. It doesn't show every financial stage behind that answer.
7.5s
39
Next time you tap, that approval message should look different. It confirms a decision about your payment. It doesn't tell you the shop has received its payout.
11.9s
40
Far Angle. See the machine behind modern life.
3.5s
Back to projects
Continue