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
- e59efde1a8483b48ae634b3df883a20b74337dc6f52da8825bbb7e59e0494270
- request
- e8cafecb08f388389472e40a8daeff1b019de5d3248078c5c82791b3e0cedf02
- transaction
- 708de876c788eb8228f8091b354de1f36bddc42796634c5351d25ede81a48172computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22033
the chainentry 22033
- sealed to the entry before
- 3ca5dee2d4620a6d74f538c82f78a823e9cac46e485e615ddbd8de58e0a5572b
- this leaf
- 13bdb4cfa986755be7bac2c1ac5bf6c84f98c9e6320f5ec7158e086fe6e1885d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- I/zVZzwzC6TiWO67IReQ6ByIEZITEGslQjUIMoGpScYM8iAy+3eKT487exDSEw1JXy7K799lQYGBhEw2SlM5Aw==