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
- 93815940c707f32f3e1a0a7613fdf1806a04ad6251a22a4b20f01a16abfc454e
- request
- 44be345a13a4bdc31f3640640ed7aafd2b66f5ddd734591307d2698966759671
- transaction
- 235a03b9070be1fdc7e222a12e0e85e39882a6833abf386e2d009dfe76f41158computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34515
the chainentry 34515
- sealed to the entry before
- 855bce38f16b85a60da0c54eae04d111cdd51b6d46a35977880e1fc850c48ba0
- this leaf
- 26ebdfee496d50e5c34540771fac2ba035c7e6ca90198d71e3e75396290f7e12
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kPT4HXsEq3Ni+owdt/ugQEoxjnrgaL2QiMSHrrULRJKtSVHF2RiVjrY6T0yI+4/D13v4429Ce3pTFMlzM1IYAA==