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
- ef87de4655cabad7cad858937bcb64910a3096fd898ed593f6c61740cc65ed86
- request
- d74fafe60c307d03c134c8032319988e029995b2d3e8528510024dd3c97afb56
- transaction
- 79ff9ef87eec72633ba07cfb1ccb70e22c6d01608ac30610287355ba2635d5f9computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 21292
the chainentry 21292
- sealed to the entry before
- 33ceae10988614713c10c8ae2fc394403549dc4abfd65b5cca1729b73fee7508
- this leaf
- f82a8265ca128e8d2fc133fbc524739ae9c9603d6a9de6fb2abf3b6de60917f8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DNhcBuof6YX5PQ08qL3iDfHZlj+lNSlYEfP0TZ7TYZNTZacCbFq90bBe7Zxwux71D7FDxE1T3eILbFoUuPUJCg==