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
- 88368f6a9301750d8a830075fe87787ab594a8eb6623492018435ff23ace12c3
- request
- d4bf2d445cea6597bacfda9ae65fb018f39c25a56a0239f72394d3f230d5b3c3
- transaction
- bb614850d04640288ac2bab64fd78c7ad45d181971b24ca48af2ade48d4bc07fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40442
the chainentry 40442
- sealed to the entry before
- 7dc67dd8ece2995d1177ec272a5dc842b9de7570dae1d92abae4089c01bcebde
- this leaf
- 47f14df3ab353a13fa7b27513dde4e26ab87b32dd4b2d01dc7da7b750dd59878
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- OKjpAs/vwistg05eg4+5tfJnGy6Xv7O+zWeeQmm/SlN+p4eYY3vnIvv5sEWuYbc5GqCXEMonlIueM/TzsmPMAQ==