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
- eb3a974912719a7c67d927cca3cf2d686a4f441e90b44d1dbfa1aa861e30f902
- request
- 165edfc894911a2a794eabcedbf6d58dad1f82d898c701ae81e35774d1319d8d
- transaction
- 737ea3c09ca47e742ae6c100fec50d8fdf3e1992bb112c90569a1ea7f7a7ac06computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67514
the chainentry 67514
- sealed to the entry before
- 01c8505c113eb34c2c2321158076889531f119d4433a87ede58289cd46732fe0
- this leaf
- bfb560a3c851a27e1f4ad53fb2894a6ea69f40180bcc49c8102b8d525a2d01e8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ztIdt+dPw2aD2wVJCByP63OJz9eQ7BK/rV/M3BMtKszBdngJsHEQb2JKUT8NRY8j5WW28w4GY70Kj6PL+tykAA==