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
- f684d1a5cdd0b0480a41c0e1255d534880701eaf5b73779b197fd8761dead013
- request
- b56f68dede9ca8635554706b23df02295e4fee45724b8c14f37228de7f19e428
- transaction
- ffaca5927a0ced2961cd496155ae501f8648a1c55fb68632d651a3c314f9cca2computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20267
the chainentry 20267
- sealed to the entry before
- bd00441897c87287f3890afdab2fae5cb65a1b53b2310050f578f299ff9b4075
- this leaf
- b5faba8ab0c58ea90212a9b31219b75dff1ae5d16b00d215137d8dc05cf6820b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Urk8u75WQXX2xh7cehjk6IZlCp1AWwfmAhgXn76UksLrfJ4VOi/SpFixY+hGwGg896pAj4sVApCgvaiJVIjKDw==