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
- 0b7dbe972b5f6e972cdfb56eadf59bdb25b4dea89999c78b3de0cc7da72effc0
- request
- ca14d357d037eb83a229e8646b86364806b07618ae0b22675d2221c19bb60a85
- transaction
- b063e7112b18f14e65ff3d0aa7948ed67db15aeafdf8f35d3d34138bd5de4116computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1038
the chainentry 1038
- sealed to the entry before
- 4bd648f779369855d89fb177a7ec33ee915e07dc8188078f1e8583684179b032
- this leaf
- 797cfb84534f42c3ff7eeb156b05a1e40cd491c5455c0bfff5637c3ad9d2dcd6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ks0AC8wEL9JQktRDtoZaA1D3nXVrUi4f4zZwnCX5ZSgivNSpvY8jRWaWZqiSzWYqh5G2B1X1tQCKjNi9TdmmDg==