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
- cad637cf73ec503466cdce8207ea7d874eb6ed428bec9a18ae546299c5dad24e
- request
- 303ec32e1a16bc861fae615049b23581b3fb4d99b156afb692e6b6bd58e4428d
- transaction
- 99c3615bd95cd0f2910176d1b32a4bb3eb03e8b53be2e43fbcf5fb19fd66efe1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 321
the chainentry 321
- sealed to the entry before
- 9de69dfc17be2c8a0a691b5ebcb5348fad6e86f4dabc4eec39b7689558e7b1db
- this leaf
- f0d07036fa95e38c405a7dfe52690d6a91600d99b5c9c8316bad58ad1e00f643
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- s1frpQygK3pRySw6UP4FUUBsPeBeR42Fx9t/BptftOKrX7mCmpZwmwtKpQHszKlnT1bqFVHPhCUExgzM79suAQ==