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
- 9003079777cecea20935f09378e019aa111b35e30335c40998db0a346b331bfd
- request
- df66554a8626abf82110ecfa1e152c8397ca955add6dcbdfe2a4d36a6d7d88d8
- transaction
- a7366b9624da5640682fb7d1511b5e4aa687267d6aadf30e755064e193096e84computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12722
the chainentry 12722
- sealed to the entry before
- 1e166ab5cfe3947be7f919eceff3e77c845039bb2d32ce6040a55bb5f4fd98bb
- this leaf
- 5a263baa07b697af3d3963a88896c1951d5dc1ded1cc9e3fd078cd41b891fc29
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kdOBMRSLpjcEA39qPPb6yB/+RpGZ4gt77iUD5q0MyF77JI3izAX4DoXoOJNBkY6EwGHcagqBmxNCy7SSvHTCDg==