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
- cb98a3d797d9ef74fda22bcc6b2876505e6e9f2a66e8b32054643c9a0ecbe38c
- request
- 41f517d0ff114c08c4fe48a964b0dbceb4ec507776b21f66da326cb06def195c
- transaction
- 3f02808fbf6877d2c404531885dda495678f8abb7667cb0e8d4af85832d927d7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30928
the chainentry 30928
- sealed to the entry before
- e7ebaa15806ac998f0b2458e71b111abc659db10f9954bf672f26066a66d4846
- this leaf
- c0df942a9f976bdd943f781ae9f61a1e0482d70f3ca1ed950390b36010cb307f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- m2KGeG99XvvdyRtcjPXL75Of0mubt3qFgfES7moSDAXZBKnhVdisO9F4WNPMtiWj8Hto1SeRFGxeUrIJM3YOCA==