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
- c0192eba658286f20fceaeec2726e192150da363f75cf90d6f9a510e1a0da432
- request
- 61174ae29bd01db7bfab1c00f7fe714952006f472fbdce2d842f1400768ce31e
- transaction
- b3b2117b9f25b969c4c9df0456068e47ddf261c09b164695a6505dd3acf7025fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1730
the chainentry 1730
- sealed to the entry before
- 554cf85f06dd680991818633af3ade9feac16ae82fa30d093a70424ffdb0d88e
- this leaf
- 289a49590eb246a78fad93ca0b4b98b25c95110e97774b19fb99d4c5b5b95c88
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xtdq/86i4FFrgvOY3MTUlNC8pxavOGngUDhxNS/XXMjUNMtko/APrx96Jmo2MgE7DHuokxc+GZ7DhdVQirV4Ag==