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
- b8a27777f86ad98c165009b050c2ff4453a8aa702a71a1c5ad5bc6ebc03b0b1a
- request
- 97fc9ca8ca23f8dec7c696c6a65535bc986bc9155223d3f0b85b993508e27608
- transaction
- b68e00d54a67efc1ed73123e7526ec69ef02dc56035b2ec4d828d2d639f12c79computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 14927
the chainentry 14927
- sealed to the entry before
- 46d7f4d1592f0cd1a0b145b19399583e5ae40f9b8b21172a1c07befbfd035a15
- this leaf
- ca3cf51984422829e77c269add45aae61a72e675c814b508929cca23c7cb7c43
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BR1j1I1HHQBD2tEOzm8BmCwIlVdzPyoM5u1rReh7hLX1KetDQ4cH3LY9IHTzFc9/68e22AN+w42WY6m1P9UyDg==