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
- 7cf9ca8fa8fa7093294ec52620c346b361053330a58e7b1b14060c7de71488a0
- request
- 89d3c96babbc4d0b3f9397568885b05ed301af3417a61c030a94541565be5418
- transaction
- 19538dbcaa07989db9b73bb483a9f1b0cad4849451b0fb94e245114ff83c4282computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 456
the chainentry 456
- sealed to the entry before
- 65631291fa98bfd79746a8603488f8577d85f1a4e47ffe85b5ca47a72c9f1e0a
- this leaf
- 9ef3aef24b0814b3916d15477d4ce0fcad5987f25d1323273ea6f5e0447889c9
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- jVSqAaX8HZhtMABO3VjfryqT4tdjJKy6VSJdrL64wtLPo5CeCevJWP3yO6DNsAxpZsqykKyMT+J3KtiK9eUwAg==