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
- 03b4789cf2b78b76f4e148b09f93d8e96692cee033c055ec7e568db11e09c1c4
- request
- 27a86690eb8e6d300508591337e21f9fa55fa24f8551208e3b2974ff37a21bec
- transaction
- 5df2b2391497f20dcc9fc93b3c8585e18f8a126037e5788832b6c739169e086bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45039
the chainentry 45039
- sealed to the entry before
- 5561d41667799daa739943b5cd5665107358984f2cddd62891bc05fa284d97fd
- this leaf
- 1b5eddb984ea3d1188a4f172f76d2894eadd81e8d0581fea7c569093e10a9237
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- VurtkrrxoeNaOqZreooGK33N8AU/S3w4jtTd2YjEMW3pJIIn6Vik0Dh80Ge1jTdwrvLfY0J27d+7NdZM5mYTCg==