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
- 9586de280f08697f49e8c32884d98f95f62191ec045d5c7f3f820c4cd3a32fd7
- request
- 43c04b1d04150ac82a53f4f65da535a8d243192060b1f014ca9401131d1d65a2
- transaction
- b896e82c5d9ecc1e37c8ac14a2929c61fdba3ec13e36d2388cd4f4dd0fe089f5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60293
the chainentry 60293
- sealed to the entry before
- bd3128430f385090c67a4f25fa39360a95574f7a2615cb1a6666cb5934d4cb49
- this leaf
- 8f448648b1785711419e22150ef1db462f971cc51de18470e40b586de6097a22
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Lc2Gyyr7D3DWf/VU4ECRso3fcF808VTJC08LrNjkBNwQEwioog2FokgnOUHJm+4sOC5lcpzMm44TijZdmxdJBA==