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
- d084a7b549c1f52c4320a29e42d2162ca2c93f8ad6a064fa4ca703a1770c7502
- request
- 08438193524c0308a9ca59ee0fe3e472cf18ca29894a4f82c1e2bdfe2efc2400
- transaction
- 937f6de038de03e851c81fe69d7442025c9b5fa7dd341d2f8fd3e710a8d1079ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40892
the chainentry 40892
- sealed to the entry before
- a377f075b35ce0d830a27694f63f16ecf781995f254b4240ebd07904a4e8c3b0
- this leaf
- 93b3cd0dd7f50a9f19f3e6145bb97eb6e8ecc86dd8330742869f6d9d7fde0c4a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DceQx0MHRspEd3uJ+OzoW4f7DEa5PS5FumZJMo5VK+pWj2Bai+L09slwx7OtvGzQc9Z/m6BukMNv0YihmLkLAg==