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
- 3ab56e6eb2d3150f70623d1449a1fc2d98b6ce8d50f11e5c165a08cfa240bd12
- request
- a5d6b2a158f29c3b2e656ecc093ec49f30aa137f78e255bf8a86d0ef59622a85
- transaction
- dcb712880fb63052fe11207e0680349eb6363ebbcfa099a35b2b9765a51c56becomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 12966
the chainentry 12966
- sealed to the entry before
- 60b3b23b12d1fc77e00a6bfc6a1006841069bd22e126e35532361673987b36ac
- this leaf
- b4be0ad133d1c59c0e1f33c22e6bbaa99f17b84cb12b12962671e87b60a90007
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D50zdfyRLPG0rXHVjgCyv9kjrGx3+d3XlR+3AUxgyRQzPP8/b9H4o8rCXvPHpxyC/kiRNJ26vKH2ykzDhqtPCQ==