The padlock and the card

Here is the part Act 0 skipped, the way you skip things in a retelling. Everyone does it.

Between Case’s tap and the spinner’s answer, a sheet slid up over the form asking for a card. Act 0 compressed the whole morning into tap, spinner, done, and that was honest at the resolution Act 0 was telling. This close up, there was a card, and a card number is the most escorted traveller of the entire morning.

The sheet that is not Traversal

The payment sheet looks like part of the app. It mostly is not. Ledgerline builds that sheet and ships it as an SDKConcept · lights on your mapSDKSoftware Development Kit: a package of code and tools for building against a platform or service. For an API, the SDK wraps the raw requests in friendly, well-tested pieces. The API is the contract; the SDK is a convenient way of honouring it., a kit of ready-made parts that Traversal’s engineers embedded instead of building a card form from scratch, which would have meant learning, and then never stopping relearning, the compliance rules that follow card numbers wherever in the world they travel. The bought half of build and buy, on screen for the first time.

And the kit has a property worth the whole scene: the card number Case types goes from the sheet to Ledgerline. It never touches Traversal’s backend, not even in passing. Traversal will learn that payment happened. It will never learn the number, and an organisation genuinely cannot leak what it never held.

What the padlock actually promises

Scene 3 left a promise: the padlock would be explained when a card was about to travel. The card is about to travel.

The connection carrying it is sealed by HTTPS, and the seal is only half of what the padlock reports. The other half is the certificateConcept · lights on your mapcertificateInformation a server presents to prove it is authorised to represent a domain, vouched for by authorities the browser already trusts. It proves the address is really the address. It says nothing about intentions.: proof, vouched for by authorities the device already trusts, that the machine answering for ledgerline.com is entitled to answer for ledgerline.com.

So the HTTPS padlockConcept · lights on your mapHTTPS padlockThe browser’s security indicator, and it means that the connection is encrypted and the certificate checked out. It is not a promise that the site is honest, and scammers can hold valid certificates for their own domains. means that nobody along the road can read this, and that the address is really the address. It does not mean the address is run by good people. A perfectly encrypted connection to a thief is still a connection to a thief, sealed against everyone except the thief, and the full anatomy of that distinction is an Act IV story.

Case types the number, the sheet seals it, Ledgerline receives it. One button remains, and it says Pay. What could possibly go wrong in the last half-inch of a morning?