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
- a462271ef6833ea6ce415268e5563d735e5c17613b50e14a9c1068162ca0cc04
- request
- ecf3a180ecd725803b8e681d543850d9552e511aa68ef529527ef17cb118f4ed
- transaction
- 53a5a8213bcf0410c8c179af4af110da409d6ae57174555d298147dd5ef9ca54computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 7369
the chainentry 7369
- sealed to the entry before
- 44ec96dcdd245a0b530adeda1073f9f915973572a619a1fbb3a6f5b4494aebb0
- this leaf
- a482cfc867ac9abb8ef8d6ea9ae3191bd42e240322706876d2ab7ab3df675cc7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- xWZ28BOYIsc5FH0m01j7WLk5ZXpZQAUyAty0fX/4q7TBGpO0c55Be4xTchrqAdYhajeUwDIrgqYytOtsCbBgAA==