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
- 151c0ddc84e07532631c8546df9540898d103637365c6b2db95ab9df86585356
- request
- 9665434f2490d6a4026e7bf710cff980d20d2badab4cee7afd9603f70f4d2818
- transaction
- e6f36ca8ef115acfc9dfea1936f24da59ab504ee6fde46dd0602495219ecd090computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 18068
the chainentry 18068
- sealed to the entry before
- f51f6aac6ed781c9ecaa7d824af8853a12dca450c892d93df6a1304a1426e179
- this leaf
- c65aed1ab601625eeb4ed4c12d38fa5fab09a3edb2085639c82f1098c9526e99
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- FInmPEs90RDkn4sr7m0fV/dFKNTK+/X8zanNb1TF5jdDEWDpxmC6uMXZxu0q+WEG2DJnjLMBBD2+vBNLGKqnDQ==