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
- f2b14fad7679b165aa4c491be33362fb27c45ad202a684c955d53dc446c596e0
- request
- e823c16edcd74cf225958c0fcfbed1beb464f5b93de415e44a40b6ab23314483
- transaction
- c5b1e7a8b054e683c7dfc6d0d52a5554317e34d2ed49460d316b5a39d00b6461computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21496
the chainentry 21496
- sealed to the entry before
- 972c752c20addd5a22fd8e5ded7e1e372c3732dd5fb63660d826362918a02c73
- this leaf
- f0c1f95379e1f72442c5a4e1d3c693fb29c70623fd923687744a95d12e583b86
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Gbvg6r9qiRJOROmgkgujIL9Wipe/0klIWEa9TeIo/efp5UQS3Et/nrip+15J+67kJZkGpzslyXPS0o6Q8uTmDw==