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
- c75d1306be454be1057076d9a4e9ee4163146d2dc7414920a485fb2f519d8ce8
- request
- c898673baea19f9b8acdd72d63fff956fee334be025c0a2006cf8d10c0930c43
- transaction
- 7dd4ac6c87429bf7617cb09121406434507ef1df167c8ce1b426a98b6ea9450ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45579
the chainentry 45579
- sealed to the entry before
- d182265499249979ae8e7334cfedbbb33f23d36352a3e4779dcef41ff118fd66
- this leaf
- 38164e158ea9c0831a0e72ddcc7f4a0bbf78849adb7ea1fcb799af473e0a0ed8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- AzkrgaFCuKCkz7VSazEQPonDPoDu+xwVKIZL9AowSNjnPqcyUEcfIc2UvbBa83Rf0/QsFg4+qdJM1rPbrg+1Bg==