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
- 2060ce204c2db63a0bad06673fcdb32a846244caf66c86d075807ea3085f4fe4
- request
- 1ef41784c00b88e477993b5e0271f8c2ff28afbf67cdd311a45edb424478fc77
- transaction
- 65717d84ad7dd77798d9c95353d1d6cc76e5d0c583fad2237d901fb8f79321d4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68259
the chainentry 68259
- sealed to the entry before
- 630acddb3ec7b2532fa2cf458c2555dd81087ed5e1163e397cb8b8ba7091f349
- this leaf
- fa1f475dea75cea52879976485f3478356b0e8cc5f33e1ea6cf1689e6365556c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GgEkBM/cfiLqEoaLJ/Ql3ocCqdApSUt4z9fe+gv7CBAVs/ozoMvXoQodkl9bbLXZSSFE9/bfTCc/O7L6Z01SAA==