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
- 9d9dcfa3f2374445dc50ebeb3e80753449c64133747a252224e72ba28f7de8a5
- request
- 55068bf292a63f6e55c81f1dc9c58be6224a907829d850af85674d8568d396f8
- transaction
- 6782e3490584b671bbf21b3154a308ccd6f77397938653b1de308999a43b3a74computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24060
the chainentry 24060
- sealed to the entry before
- 105996daf4fc306f90319488f281b678829a1026404b7fb739122b429112d036
- this leaf
- e09a6383c2b20df544342f07afa18a3f7af18adfd6879aa9bff26d348fcb59cf
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- z1fL/UVquKz7JdMRVplcFQG/Z85MT63a5afVWZet8DXZU3UokrGAf75sfE45ITp1HSv0SKwuinouMy7yHzmVCg==