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
- 3a45ba87c30d77bee48d4b4ac44a687208de14b185f2ddc5451b673b263f2867
- request
- 49238b6f393a180ccac64000f3383c7a73d8a62c9f7054e900a483e8a11a1add
- transaction
- 85d5c10a4623a9771af53d00343f168920ef9da579545d79a73ec499a76e534ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64143
the chainentry 64143
- sealed to the entry before
- e5bb17a4185e79ad1c677de66a2c2c8dbd021acdc8ea7634c987ce5a1bb09438
- this leaf
- f2cff15fad1e329107f28e20bdd86e52ef2a234ea3d294aea94d179db3ebb6a5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3g5XHYxRWUbR2FoFM2JkQuV1CazMUw4M4dBhHxBV6kLUQyNFlj3UU68CsBXuZS/G5/ts5PkH+ldTTlIwi6TfDA==