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
- df4046bbaf6f720b310f48c4ca6630ede969e866cfeee208f8cddee85a8b2bfc
- request
- 93e7f604037eeed95d1a7f107448ab91167d8787cd7e7555e7ee67a6c16e6294
- transaction
- ef7276b9e21e64565d2877d2ae8e1614aad197dc54273b571c7c53e8ae5437cbcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28193
the chainentry 28193
- sealed to the entry before
- 87c82a9a63fdb85aeaf1d00392e6ac890dd7a2fe69a4557e13aa4d7baad002f2
- this leaf
- c8f69f9cf7dc28e80f6824690fc6cece363b49c21b04ae566d32355812c44a37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bWD5jk4e7w6fC1/uxmMkaM7shEbW9mr+GGjErZHPjq93mvS7UdLdUs93irDXc+l11Dllo+bMKZa9O97uoG4yDg==