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
- 5f65f0fa4e0b71762d647ab288e6048664beaa1d8ac1b71b81bf1a147ab54850
- request
- 85fbdc84ad12229f5fea5728350b6be13174d42dba147971121b71beb6521892
- transaction
- 86771ad7820ea5609e6e1c1d5449ac2a847224d6887375c9db0001502accf240computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42885
the chainentry 42885
- sealed to the entry before
- e92182246a078fe04696d0e9381368867858fcdd9bcda9ecc067348d7dbf7678
- this leaf
- f0c342ad2a3cc9a3bf004dffbf0ac4cb4ec85fea8ab339193f186730c1ab1530
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2FwQ0zLaKKLtcZHtoYKtOtJ8aKl+i7GpmxKglQWdqvjOiCuQVIgelkV4YTeuWYXyF9EEVCjKPc6IDIBluyZgDQ==