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
- 9a8d646570d36672802b54f25a98ed2526238ced66eff298b1439e0d302760ab
- request
- 85496d3cb0ab1100c91cfb4f2b8b90c1be15d7e8be250dd6e7fb2f3d20e97e31
- transaction
- 0d4c5958a1dacf7a882a58b36829e1a2cab3e8b56f44a9b6b49a5302254a0bb0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7052
the chainentry 7052
- sealed to the entry before
- f957dd4fd80898c593e6b97cd35e912962696154fb88661c49064e5b6cdef16c
- this leaf
- ada2ab39196a247e4b0f32a93679f95e104e9ac9eb707526008d141bcf91f671
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- krimtEL1gmbTHKvbMIOU4GXvuJfeFkTyIG44Sus5RQSx0i51MEqILxeLojaVocR5hKGeP4PUbxuFVY0JHkWFAg==