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
- 50361467729c02c8dc8636406bcbb0529a7783d689554931e41b61926f4245d8
- request
- a511c8e5083140b07d4960e77f810374960189d641a5dcc93c27749f9dfc53a3
- transaction
- 19d687ae3aa418b933040e634efd4d7cee61a3f4ec728413ec0d338dabe352d8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 16460
the chainentry 16460
- sealed to the entry before
- 74912c8fb837fc2a04c658f84623cd23158129414a225b621789044fbaa4da51
- this leaf
- a82fc6fc7a601f854e79b9c21dd9df3293293b29b40bae8a809d577a5ccb2254
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oYMqDEpHJD3TkvRG4pZjCEhcXvF63W1i2b5uX7xM4yizCq5+GWxF+IxAuvacXwGTNSAqDtf9xQ9sFMrtNBVdCQ==