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
- 8a952a731f3bebdd09b84c05731ee01be5952e19897ab8293003838abde20f84
- request
- 18b9ff25c973977875a32bdb0c7d73c385506f455e9eaa695ec7173f0af2a3dd
- transaction
- 8debf88fe509e5c90addcf2f399fc015cfc383cdf742fa0ccaa6d09df3089048computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64313
the chainentry 64313
- sealed to the entry before
- fb97c415e4aa55760972778c4e08533c31c6452eca77a5e12f66a1a42cf249cf
- this leaf
- 8c7962060da592c99f287c20b8fc39d1eb1297e659a72c6e194d0465e73fc76a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- yQqAQ2B4aygXuQbRe9ifGH5Qhg3iuYBHL6sdmOlSTMp99jMTlKWCNdlsty/sTsn1DeVyHubluuVcd1lTPTtiDw==