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
- e01d741ee307cdd4993158dce7905dd4c78a7cea256dbf4bd5df77148d711411
- request
- 081970cb1be3db955914e1dc95e662a6eaaea2513006912ef81fcb73ff2b9a46
- transaction
- 788189fa563b725371c6a1605e24a6c65934651cbd0bf42fdc16b24360264f5ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2185
the chainentry 2185
- sealed to the entry before
- b620abc0ddae6679f799544318e215bfed5b2d8cc2a896c12484a1aba533fb96
- this leaf
- 212dbd281fa6c2ac6b7f20f0d80a0545b8a5cc5549817aa96204ef0bd258bfeb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XcpJRERvYPG7Q77mGiBuTB/O6A30XKeQproO+c0MNdsDZfbRP58V7U8BetwhTXUCxA/pPPifEaUwyoxkyDKECQ==