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
- c5bf6d6afb2613e2a67ef04e2e0f23d157d2a4587b46ec9245f953f36ddd3321
- request
- 298130c00e3ad5bad229e5db652db06dd121648eebcbcf40d4d8403bfcfe77e4
- transaction
- 7095b12e479ac3a63f3818ce7abad392fbce4222ec51b2c6a764a1422357112ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70016
the chainentry 70016
- sealed to the entry before
- 421f8f972d64edc1ecbdccbda28983762299fd57ed2127642b10aa22323d0df1
- this leaf
- 044696b029bbe1e95c6022a9b7fe6388167a915d6ebe242fc816c1cba63585f4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q6fcaaXtmpUDhoFRfv2Q680qiEWInoALHXsmrRhYYZqMW0JUyHlHmlpyLl0cGvA3CxI5FGPpdTjCJ5wbS8NZDg==