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
- ddac8e2078a35c6e4b35853ddcb82e85889324483d129b2c9bce4df328c8f426
- request
- 5207f80105bfa85040fd878b481a589e9978c2417209e83060c45fe1c0f9756a
- transaction
- 128fd91275174810b12693666093087187b3a9a81bfe8f92e9b8bd56c4089e45computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24118
the chainentry 24118
- sealed to the entry before
- 2005a80f84d66d779bd57b0759a26e2bbc1f2cfa1c22c0cb2f0d74a96ce83c36
- this leaf
- 4e3883f3191a3ceffdf3706f33cced27809952287a35ad876f9ff40cb04e5795
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- v4fXCVvCvDWUYW8F9rD5wnuo/88vYyF/JaZj5vmBYrGLIpdrqeI6awWLU4WKoEZ49siJFUcGb1c/AsNf7vrQDA==