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
- ce78e7e474dc327f5885109608b1f33292dee49fc4a944cd0ed4e255927f04a0
- request
- f9dde990f72843da7815d4cf01add2abf7914dfc0640ce3ae4e24ae24661d31a
- transaction
- b9cd9467433909f95fa4bd61baa903b8e8c6b4ee6d87bccec6aec793c42acbfdcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48206
the chainentry 48206
- sealed to the entry before
- 7295cbeeecd0086e4b124393b5a703994d664430122028576730b8d1b50dc39e
- this leaf
- 9c9f0867d3e8ad887dcd57cfe20507a99e2737edb112101752e6795a1435cc14
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- MAT5++oAYvAg1KXFmNfmqpoFxIP+foYl0sqKGPLp63haq0r7duecXIZqIugo9VxNYk9iTZcTj9nSVMmzBtaMDA==