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
- e154c345aa3bfea9527db01be1b44450750f15c3c3aef2b45a928a37fcae4b18
- request
- ab1f6c9b1da88a2e00a2bdde636c394bc7349290c1d6d2938f7ce10b20c970e4
- transaction
- 39d9d11b689d812f95f03f9a7ede31eb145961779030884d6a30d67a58fd068bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46984
the chainentry 46984
- sealed to the entry before
- 0147ee0fe7c50bd199d94e914b927234be7ff5463534f50c09f8e295ca6a37f1
- this leaf
- bc754ba9e23030c2a183fce3e73e7d7dac9b74b19c077b2c5252f764f07489bf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- icXjugCtnb4e4PVOEsLSAbm3NzPdxe5SdEkghYU4kOBCpWh9R+zWHNWWW5cFkHCnTc5SANU81r63ReolJasFBw==