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
- b849086ef898ca145468134165d6dba501d15edb458ecfc89924d676b2f1c263
- request
- 4cc39ee92264afdeb704c1be126782b1d37854459eed3097f74e5f438a1cf583
- transaction
- 28e44d1a1456837b2c9ed229319c7a49740fd5a1969f85a22b1c916b45a07064computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17966
the chainentry 17966
- sealed to the entry before
- 3cd96376dcf90d596db33f74b3d922d5ba9d1ea10e2e4777c8b008ebb927d613
- this leaf
- 1d2e9a39727e4a812374033d7470163dee24d581eed966373016df59b585fc50
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- mt4kq5GHGA9wt4DOL0ehcDwcKWEoGQ96dH1fTKKY+edtt/asv/pNo9fTijpoZynP483iUSYUmzmpqk0UCVruDw==