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
- f374851a996f92d8088bf87d2733bde1fe693204aa480970e73db6e4fb96d113
- request
- 23cc501d6efdf4d9acb4b42100ec8dc6872ca6cab67801a873f117939f0d9c59
- transaction
- 7cd7367e378cc18a7e7dcd2321a06141c1eae40523c9bebaaf365474b40f717fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71146
the chainentry 71146
- sealed to the entry before
- 45e055ad1d403391f20ab3ae5cf475d48c0331fafbe66af8d7291f1d1a3349b8
- this leaf
- 5ce7e1957f768acc5d7135e3dc01d7adb4208f840483f0e50562afb61031ab37
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3fYO4kPZMshf1Ab2guM+nFHiAQhytQrqAGfq42cZByJLujlcHhfwe2GZH/m/+GOAm8bCC9wykXMBk5rnKU9WDw==