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
- 41557bb593767c2b4f6e09aa6114658fb37e1312e357a2343a5b40c7f4f47fb7
- request
- 0d45dc013446ab93b67cdded52c1228e31c903ae5fa4f7334721e98e41870cc0
- transaction
- e3aeb48836962d84e0642fecf6a43fe4136f077ef54bc134b122bc93e1999730computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45502
the chainentry 45502
- sealed to the entry before
- a7ff91234ca0041bf549256e35e470316e13deefedf7cc002379c71bd9f66a78
- this leaf
- 493b0cc23e37590166626e0cf90adc26924d379e86c7570483043778d7ebcdf4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7sLQw2UGo0SBeD23BKOenKe4cyslvYvA+Est1JHubCSc2PLAcumPOo2mRmzmbLVwhT9KXaQEz8RIEOYITnJyCA==