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
- 90b456017d8c814ba3911b0dede7cc95600f2be66fcf6c3a9886146654db4997
- request
- 49187647fe8576969a71a75f201e0d41874accd858daaa64a2ddc5fdb584ad33
- transaction
- 4ea13d6221b320c907ffbd1ccd21dc9b49fdae0537884d869c732393d125f0a5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64403
the chainentry 64403
- sealed to the entry before
- 160b443ef74e7569d205562e99cc9b1c6d7ee23fca8c64363aa8a0a2c4f813cc
- this leaf
- 6de3900c16d9892055279ddc614e03d7174595da1889de4294b64fa427b4f5d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- K3YmLEZhB/Xw5lZVSlZQUJ4O0+pmh4ZIuL90GmD7LV7oFs2eajC5AOa0VZjaPwPZAMNqZGG+VDUCJU3zfGQ2Dw==