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
- df295f413a1d8598ddcc68181c0c070162641944ad14afbf8adbd030f899b400
- request
- 25cd385298abdc9816af5b381dd1d0b2f5053772eccfa354e230aac50ed1a66b
- transaction
- 8ed89aff89493b983cf808e41d1b7506b2d6c8a89ab2c4dd596f90a6221757fccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 13036
the chainentry 13036
- sealed to the entry before
- eb209720da3cb4d6098061bf651645e463e1e55630ed85a99cf5a0f81db29d38
- this leaf
- 6e224fc3c31957b5e0931174b29bbab57dc40239efede5e596436aaf6f199374
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Nm9I9AAhTZVHZ19d7VsE7ZKSjoKCpD9mrVyOxz+bcb2IGjCiIHezHkybNA9yr2f9moR/j9QJAslOFz47msc/AA==