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
- eb31c1280085a1ee7c5163c027d792c215a72a17180db32504938dab4bca6533
- request
- 1ce13baff5b3a7caed9d1f01164e03255c9736edec986a262317286ec8f3dab4
- transaction
- 67c396f5fbd57c989446aa78e5d4baac702b7b6c6585a1f2a5ba98a41d00144dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 71518
the chainentry 71518
- sealed to the entry before
- 35b96b38983e968b827f55da3599c982af73816021f73e7d91e906bfd69a5b0e
- this leaf
- 7596146cc0249d3fd25d34d89978ff6f21e3c9d371ddd73fa7712f4dcd8aa77d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 7ZWVkvgv9fQYl3YBMJQxWZ7Ih2XQiEGE0VhS1Yf4vrzBf8v+74ujaUnWLaPjU6Xvnub6aiOfw3mmOgJwgfD6DA==