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
- 5534e3970882fede4ff47ffb493d466714c90b7e0ece9104e3cacd9117d59ff6
- request
- 1fc735a473a55fa087510bfc12e65b2f154f36ae63530a4c20b37c775617e4f4
- transaction
- 168d27c78d7385aefee77fb6cfdace1a96bcf3fb057886186c64361038fd599dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1525
the chainentry 1525
- sealed to the entry before
- ff0c4f883e09a5d02c8e17d4be6b8085400fdd48f6116e3ad697383fd5a69eb9
- this leaf
- 61f5c473326d6520037d244b921c67d10bb94334a1f82d6b0799ab3e5d01b430
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QDIL+qlZGBCIOzaD9qqSlj+IhdFb9X7QKYSk/+oPDLm32S/Zik5LG8l8+UBiildXa98gdiiq1KQSE38YJNBCDA==