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
- 0e2d16d70235a05c07184062cf1dff01166fa12c5619aa7748919c2b3f738aeb
- request
- 610cba64f7fd04c9c5a3e37f6b724ab046e94013a319caf9ec7033ebc4c78515
- transaction
- 96262d28b2a9d127104ebc0636aabbbc30a451534fe634a2ff1b636b510263b4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 536
the chainentry 536
- sealed to the entry before
- 286c2434ca6a0e067745b752611b367a881702bd2e5d9ec219fd9fc0875ea96c
- this leaf
- 58eab7f4d165019bec659875e0efc06254ebd9bad2333d1691b48ce6b4cd5537
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- iS25p6u4sRU+/GoWu3v6ttxcW6cH+QrxqlE9ZBZ4FX6S+Wm94Swe1gWfyKf6D3eTp9Dr5S4g+ZNOhwT3VpOgBA==