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
- ca3be1bb8383244f39de4aacb74fd668a53642ae8c684a3ef648cd4db9e9d26f
- request
- 4cf8991e6f12634b2bf0e1023018f131de5c61fcd68a17a8a73ab4c480a29fbf
- transaction
- 4db43f54bf06f3a8a2e6a081b6c2ecff381f1691cc6ea838c134289703df69c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64959
the chainentry 64959
- sealed to the entry before
- 379a192dba80753e4b572ae9319985c5df894db16374c03330eecd185f88bfab
- this leaf
- 08f5594d7fbec31ca8d243fc7f9fe9b358098100ff7f6da1d592fd726ef1bc80
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- pAwlxPf2iwlyUQ2EY7yx5450zjArGn/pVUxYrSiWvx2A8Xb/+UCfeeFrhpZc/Runr/Gz5PEoguUfp18tSC1cCw==