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
- b4c02e6885db05fda2c36d06eec2f4b531b5f7a7e6ed220554d5d3558c9fb3ee
- request
- 47d1911a856eaf6afb00de42282ad3e69e7db5c89451518baea334e13a2b9ec7
- transaction
- 20e847ca7f23715f49f37320113662295e3b0c376f665a472b0f18ae50ad9ab3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 3042
the chainentry 3042
- sealed to the entry before
- 73fc3ab1971a865d476404a95275c13f8583f0268edea9db45455066c9c4e7d5
- this leaf
- a1388661b8bb310f4ee39d7c1b1d181843449cd06413abef3ab8b8c1c5d5e03d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- U8xqFBLHynuJXFbL0uYnBKxdeQC3RK7WI4oQ4i0kKM8UCdK9aQD90qE6Yrz7O0uP2KeMFPVJrBX9tnFI1ExkAQ==