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
- e1f5a694486313f96ecd59b087b9a124c4599e644f64925417f2932535132c86
- request
- 214030106faa3e7c6fe5a57fc8ad3193f1ac07b4cb2bbe36b0dfd9de1159f956
- transaction
- 8c0ef7fb36fd69d8780db49cd7d5f1af663790ef32547e49767f278cecb6106fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 40869
the chainentry 40869
- sealed to the entry before
- 75ee47230f0573eb252cd3671f109e28818a502d94c852af1c372fa0d8a73a68
- this leaf
- 239b5891ad4a0a9f5499b55d2405039b96f77d18c2022a4039cac3adcc678a30
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RRhTXrY78lozj8Xxdq+2s2makjN/w6UvTiE+V2TKp2EXDbk2l+wP71mDlvPBUOliGSexKvCG7sX4AYyA84UjBg==