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
- a10952d508ae79a4f19fd39a09dd31a6ebe98ac13bb1e48d36109d66bbe2c30a
- request
- 5cfb09908e217065c8aef14ef4dbbe432a30a7e8c6c89fcf8423c77f1acd4d2d
- transaction
- ffe3cc48c2ac724306b81e7156dd564548a066a4fdc6011092491a5bb2feac45computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 67073
the chainentry 67073
- sealed to the entry before
- 54fba5aaa640aae3e121d89a93e496536b75694af2c91fbddd73ac96384d6f16
- this leaf
- 1a1f29dc3d0a5cfd25a53ad2eee45323335cd3f73133c55f380c3a59f6ff7bdd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Pj+N63eObFui6EUciEu2yNA/wte3TyomRfMLG8V8LtPnDUzlh5sKk2F7kdCcrzzPzYKKC7dpEwxMdOuMWPZBBg==