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
- b0cc2a06b942e6376b296c1318f3c9d40c5fe8ad2c8456c350184aff103a4d34
- request
- 193dec0efe6f7e46c5aaf790d04a27fcaca739592ff74885fbc1787c85c41cca
- transaction
- a6b0504157ade743fd4a3d776c0f36a9bbe50c5604e910b6d0c61445b2143148computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42596
the chainentry 42596
- sealed to the entry before
- 89413f9eafa064c82df326469675774c0b9e8e28de1d7a2069a6e718302cc0a5
- this leaf
- 84de50671b0c2f2ea630fbf29083922c325331bf81be1dae8336550476938190
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- HHNrJSEfMEEFz9AjDrTdzq+/ik28hvxRN2q8JpipVWuJBDmLPaqsGjU2NBBMobgkRsZgOeOg5d64E6FO+J8WDg==