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
- 8eb057a7ec651e0e85c59c4079c7e164b1722f51fb630d13f12fba363716bf11
- request
- 100f884f083d8319e4d713fd8cf0811f0da62739f4dde8122756328519166e11
- transaction
- 198f19b857e180e5686f0387e210e269bead0493a6c2385cb9817ad2159330e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21556
the chainentry 21556
- sealed to the entry before
- a52a4d53914745cd2df9b53ff46f5ab8d735bfd177e9c0c930f87faf2a9d983d
- this leaf
- fcf20ba460a84c9392a3d67a8626264d9cb62774dff6faf7b0ed633e04113b23
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- fx/bprCvcyTTK5Sty4cdX2fo7JL60WAe7mI9KicBm6pYQWe+g2VufyoJaHu18c61lwkWBJy1p5jxKWGoqrz0Ag==