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
- c7e4e8fed6fe17bdf707a9fedff24ee310095f1c7bbfb1620dc62bd43ceed8dc
- request
- ffa566d4cfe8a86752f17a2626854e5485b4e2863d01aadfe640567a66d2d933
- transaction
- 5a193ec6a58229433d5b3bb35d4092e79871f6dfb035e60ba683d078280d1ba7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56658
the chainentry 56658
- sealed to the entry before
- dc66048ea703afc2e7e11c6bb8b08375dfcb19cf674c69df2a66c80467ce3a05
- this leaf
- 7c7bc3209070a46c3807c5e635c5c8fefec2a7c9562e0f53b97f697a4a335e94
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- c2etr/Fk9fGYX9WA1mVgERqGEFa+7CGSqLGXAmj7K3bptU1bELAGjKNSKcO9AcyyW2agWVy3IBBab0U2yrZoAw==