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
- 1663ca76b0911284c2f8a07fe5b5642fa566883f00ebff309df11b891ccb044a
- request
- 0241ef5a9f648ab5f53af9fadb588404a03f9d8e819b3f711d6532bf3eecc6f3
- transaction
- afc5d101173a292e9553fd555e7cd72cf9e5da234491ea790565ff42281cfa02computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46611
the chainentry 46611
- sealed to the entry before
- 8fb73571df080c5c03a5ff08106cb66239702344ec2231fb4168eba41261c118
- this leaf
- 9014cca4863bf1f8bf468558148beed5f884249b7f0836f8cfa74a682db2a321
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QF/YgsqWRnmm3CrPxiR1Ss64rdZq0TR7PVM3RJ/bkt7jIbLtSmaUbHn4j04DFSI2hBNiA7Np5EQB/3b4x9ndAg==