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
- 16c11f2815db75d3002f1356c657716a8bf5784071da268a3bee6f1fc1e4811e
- request
- 8fd72f744cb0c431f9c7eb653a5ccc74237ac863d50784d44d948514efe13730
- transaction
- 532b76b9f622fe49297db0bc4691fa86242e044d0b091ad3427c1864bf075584computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 50882
the chainentry 50882
- sealed to the entry before
- 98450ff27289fd188cfeb64f2b329ef51227206243eecd9d63eb47f80b0657db
- this leaf
- 0ce799ebfd316f305d9f02a41fc093cf1282c61e84f4edf374320747355bb4db
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- vDMAhi43KXo8MBKZoR8R0vFuhE3KVaMnIjmzsrjLXt5Q0BrDJrDCdUlOnae/tIsodYjPoGAjFN9owjNfKDHEAQ==