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
- 01957271199267c2f3cfff6897c8a387cfb1e4ac86e652c37598343054d00baa
- request
- d0dd1b1410eb6de845cdf3fe8bfea87454abc9c30b85ab9c5bf5757eff758966
- transaction
- 7df9f2a05a3fb291692585cc441e4f0ac26d1bf9eb5d15bc27d16c86647a5f9fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42428
the chainentry 42428
- sealed to the entry before
- cab98f7e840beda5744b5b236c493ed17605070dc05dacb7bba78d151553c31e
- this leaf
- cccc5a2b6ed4a6f6043d64da09e7646bdab3927f9ee1ff6dd5e9fe709f2b7e1c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Y4ucaC4SqBcysCf68NZb9+y99I4xwyAvl6IKO//RBLtCx5PH0IZgMV+jwWk/y8v0DmcRZW+C69/E/L8csFYCCg==