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
- 3b6a937c3df0d7f25f0bacf048bd467996a25a28a694c4f54f4928a068619335
- request
- 13a71742b55ee353561f392ce2b26591a6f3869e255537a141cbf0d8d02c2c45
- transaction
- 971132173d52c0bfed63acd9dd438411b1bed1fe3c138a2d0d48f923c2d248dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6292
the chainentry 6292
- sealed to the entry before
- ec5b0a1d0cbea981233686ac21ee557ef82b17b0fe22807873679c26f9538dbb
- this leaf
- a0739e5c02298e285b9d333298267c9e1ca326b2a37089d65a2b4dff7c9e6557
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tGpdRaZ0y0fQckvy/FtzxCsQTaoz/l+l0yPmAZVLh/C4H6owT83cTge2L4eQLWo/O5LUAmbTLwCAMb3iAbq3Dw==