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
- 7dd43439f3dc271ee20fe84d2aac21df0c21fea6a63aaa9eec0984b6aa4bf67e
- request
- 0fa34357ed5b05c4d3e0db2cd664cc1edd2b8d02cf35dd85521e9d02b073ef85
- transaction
- 0f24968f284e29d4652831682b4d4986848db2deda6d08c8462d79d98db1603dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17243
the chainentry 17243
- sealed to the entry before
- c0e5e72a830c8077b4fa667f8a52acd1c4788c42ecfc7352fcfbb7a348240030
- this leaf
- b8b5f80d809f387834eb2b06388ba00a628043b9413fdfb18b70c92b9bd8af70
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 17xIJtVN5nBE10bLjyVOLCfUd3EznbapcL7U7idXbAN5E/zttTmqpYvNPTegB3WIaTc5jnFweVuDO+6h6zZhDg==