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
- d7f3456f5b6d52b538c18f0907b62c1cb4d8ab0fb6d90ecca6c213833b7ef19c
- request
- 259c352662c5bca81b344e2dfbdebf105413ded6d8b598151c2e57cf060d2bc0
- transaction
- aa635b5180ec8e2793797f9050c4579693d2284dbb0b3c9233e4a575bbded027computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 37309
the chainentry 37309
- sealed to the entry before
- 00b1bc6cefbd3b4805e7a5dc2931bec6342d3d9d549a9f426e6452194ea5e083
- this leaf
- a2604e2e8c9b281f423f064820dd623358aae55853397db83de2f7435caf4bc6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tcp1ISEW1ujDRlt1Tf2DpzQ1dP1XXswsgTNbszBJLmTLcQ+TckZj0n2Ju/40isBIeEPmv70IP7MYgU3V+Vr+DQ==