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
- d8ec53050ac43aabc548c4e8be1792505d0fecbaf1a13673d3d4b3bc7343c050
- request
- 329c2ef211c2024ed3633e6aa03fe843d7af9b06dc79df1016876bdb8f8a8be5
- transaction
- 56b6a0d95220ed0d8fdce3d943f681687a6ef8c49150262ae61c9ea1877dde00computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26001
the chainentry 26001
- sealed to the entry before
- fef87dc27e7f6896d2834a0ced216b3e16c88ae8b5a338980f2b5269b49d80f5
- this leaf
- 5930a008c9ab8e1807148a702765688d667928318e700a0d9c06451d373c0dc4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- DVtKuHeT7DBM74sbtUCkrlEXa+hCF99u6iafl51fkacxjKK+TSWAs5OiMThVsUNSh2aH+KfdZmmkcw/TL+74Dw==