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
- f03cee410bd69c56b29316953c7a415878e8a7eb1c2528a1f13390f172f9d6a0
- request
- fa2c34ea5f423b5c5237e7704408c5f138f859fa39d05a25d12ccbbb20bee865
- transaction
- 7d2b432a04ef65851f19c1579438ad29dac71c0749314966b8d7028e91ccaef7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 8165
the chainentry 8165
- sealed to the entry before
- f7aa3d27863f3117d93f45532b2cde71621ced080532f33cd7e73b0d2153862a
- this leaf
- df9866313f6871bc6b918f447ea805c60d6e29755a18187dfdfb639ffd029f71
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 69PTBGTEQW44wvFfWqGhUDTVhs/ctFMrYh0/mJUVSbaP4wJnKChHHytGUiK7AXjHVDpBNoA/OF7TMmbwcxiYDw==