why1 reason
data_leakpayment_card
payment_note carries a payment card number (41************11), which would be written to a permanent public record
what it was decided fromfingerprints
- rule compiled from it
- 789ea675696f8779f3cccec1dcae72d2aa9859521dc169c9500c8b923a49ce80
- request
- 19790a374e1c41d89b7092b6cac5a89aad589180ec95a87e4a513a977c6a1b8d
- transaction
- 5c9b07e3bfd8030b5f4e421c6de2e0d22addac73347126599b06b5e1de16006ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2839
the chainentry 2839
- sealed to the entry before
- 08f485dd6164b6ae57b4e7ae930371cb27fc371512d5d608070e8f2d4e68a7ca
- this leaf
- 3050525e30319792b6bc100202cddf2a71033f3193290a26940f1b04bff5e6da
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- CTsKc3UzgaQCAELOCojgbzKRZbOnI87wGC0ZgzPUQBEqof8E+ChRN21aTOhEpeK8xvhGV9+2W0yMqM1iYFIGAA==