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
- 7d9def961fe39b0a6f81b16b3838cc74c70dab266a8f55c10f6caa714cc67431
- request
- dbe82757b5707f861abc1a8d5577ece0d8be054e405cf4333b57935b456cea06
- transaction
- 6c8748e093e175adb1131696367e549575a8fdd918e153448a8c09bc42066cd7computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 601
the chainentry 601
- sealed to the entry before
- b4e381d30e5b36671fbfbf4d9a27faa27c9bb43ca83b8fe71d9b52ffbb55488d
- this leaf
- a28de6d1db949626cc7066164e23d6bfa65c1ede5c95d654edfa995aad0cae1e
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1rajd6ZVM169tKIqd0KvHspgSwyUrbnS6RClGM4x3hmfJntrJVdNqkvsXStUuM+gKJ+6IV+WCPozkPF0gwQqBg==