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
- 6a8291b8378e4dd4f1b46c09d803fe4c38caf04b801b3cd73be2c5bbb1c57a94
- request
- af3cb359a8e8441fe377fb9feb10e6b80b1687be670c26b41f314ffe60e876fa
- transaction
- 7de5c081950be7a7d7da2281d4088c1c3ccdd5260054e400ad61a08da65ba51bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17721
the chainentry 17721
- sealed to the entry before
- 4ca29cc130d2f770e3660061fe92a8922317699b2d49702c2ad5c360dfdbc90e
- this leaf
- 46c8913904b45c83f07880cf901be4f3bb63e3c8ea7a3a19eb857289698c8d36
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- bAbjxrC54rsqGImnu8MtOX0MWUYOWF1VPoz71H4Cp4gyRJ1eTCCD4gFJ7IFZo35CEs99mtj29iN3MKo9KGm0Cw==