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
- 5e2f685fff2ede4f3cbd94f7041677cab8fa1980e536d41b347269d0158548f7
- request
- 8de2f3f6738f0e9c48dba195a7ee6750cbd069be3fbbdec5ba7cc9fcfc272aaa
- transaction
- 28ead704443018065ed37eba55da05fc7b1daee187f21e9ebce0457507e32e7ecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52665
the chainentry 52665
- sealed to the entry before
- fe1928ab8b265df04bfdc6ed2b3f2444084817e6b6f5d0d5fa56c15c9975b9ae
- this leaf
- accebb1964ecfdc45f8287681a869cb6bb2dcc3402f6c857339038f7487734cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hPlUNa+nhdln3PGLoInkhYa33xTUTxzTPyhWhXivwfe9lQ3emGqHtPjmTlsac+iUebyTYVeOfBkpE87QWEawAA==