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
- c24f78ff3a4e306a228e06dee40ff087b9fe6eb9c4d87ea2afb2c5f9ada4dd83
- request
- 4eff248851bfddabe4ed1816351097a0a5ecd6de7f6f643c69e75adcfef801ee
- transaction
- 5db15b80be41a1232a4fc5a88bea297c0ede22c4e8e48caf8fbef9b44f0bcf05computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46518
the chainentry 46518
- sealed to the entry before
- e5bad9b6f87167462f6180dab0e088825b0fa07fb5399e718f94a8400bddde93
- this leaf
- fe2e422176802846b447e5a4e79734c9eaa5179d1841357751bd10f3e4a4c631
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- cBhvIlyIjeAPGcTNU3/6hpUKyBH6LSwDj2UWzEPIQYQpeV5xdQrNselAjE7TuJRonTpL7T6onL2KjBbEG+flAQ==