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
- c0ec0e3206f57cb8626a68f082b55a6cedacc323b4e18d6833ed987cf5c627cb
- request
- 6ae468232b31a069ae04a80a452d61ed58193d1aaad7318c970b8cf6a133af33
- transaction
- 2ed09f695d29b83b10577859de9a0a99612d96b46a00ebf5d64db498a302439acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48071
the chainentry 48071
- sealed to the entry before
- 69faaad9d9a0088b7bce93b9b07c23a90f007879b5300af94649feaab250ae54
- this leaf
- a815790ebeeffeba8ca8946ef21db23c417f3ba1fe7066ccd637c71538177ff8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Rrqcmf6T2aYiEhpg/a5fqTRNFU77LyiOGgCsb1Osarui2FD5t31jSoT8q03DnJIYIlJY4YUWIDTQt4Ehru+kBw==