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
- 0e0b72f0d56c81a31b97121769703a96da8657014efa22d3a6f5c3785275a617
- request
- 5fecd55344e90a1d0f831f17eb89452ad599f4cd870d90cf78226ec0bf95819a
- transaction
- 7990662565d0ab79c71ef7b0a87659176b60f9c95fe5ee385eb9a6f067a99ffacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56752
the chainentry 56752
- sealed to the entry before
- 6ce83a5eb8ef03fdb2a3862c658010af7b5af2400c616520aea5a4cbddbea3d2
- this leaf
- 3daa82060d9362eeacb459f0650f48c4d3dbac692bddca0e071a8eca40697c55
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7XTtxYExA7+AiEXVv+ZfAwNdMjv7PvWdLvc7mV6Sx+UJcR416y20h2iQfwYiXhpdBlT3FykPYWsrI38Ob/O4Bg==