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
- 032aa3129980809c18836fe5bf0224e2ce184f1ff5054a4ea7846482bc0c844c
- request
- 77ba153493e156e110a815dcf3a57d3aec2d57dcbb9681eacb428740fe5589d5
- transaction
- a1541f2a350a872952aeb767fdd3c12399454822e1dbb371be13ef590a008cdecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 26417
the chainentry 26417
- sealed to the entry before
- 0ad5df8e3df2b946e5a91479d2f7bc3322163e7df4a28100217c025caded30fb
- this leaf
- 1d827ca56be5be35e1e6d06424f8c0ed625e0400a6395984c7db248e454437ab
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- QWs1tX6O029il3I3S/0I6gCl92JZQsMFwowcQ0Wk8agKfuwg36xYuQOO0ayNXFClESKHoE1oaM/a9OMY+IPSDw==