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
- ff4930c2ee4d451ea7e1a51a994be07504fdc164b9eff475319b6173ead9b981
- request
- 5b5ced7034cabc62c43f675d1d07183e7693f36da3cb7ed713c8243ffff696c1
- transaction
- 1fc1bff133eb9952715082ab8824d159297edd6913528a180eb3c870e8da0770computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 75833
the chainentry 75833
- sealed to the entry before
- 9a2327e324f8212e310234920796a4cbd3c7ae731f1d0a206eeb335d24723216
- this leaf
- 7255307f849f68d3dc7de5e728b91849feaaea60001479ecf19fe1f6f532f497
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RCzMYrST+hAwifBx2Ehf3mWIvbffegbGSuwMEIgzeaJE9XKvBl/rE8bfrSU/Vop7CIhgde3PszaNHMF+xpndCA==