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
- a1f814d27a104239351756620bcdab2c431302c859d305edb8b90b5252993fd5
- request
- 20f4774011bb2dbcde9ab4f92e2707e0650233c8afb16d2c14a997bb8327bb37
- transaction
- 185e9d5dced4694a994df7eb0fd03876a5c75e84d66e06dec92ddc4e5af1ca5dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 69906
the chainentry 69906
- sealed to the entry before
- 3efa69852817991133382f5132682078e5210c5c623f940b43363b9ab1ff4e79
- this leaf
- dc15260847f19d463e4c09964063f1251f4084f21cd3d97e55782de364ed881f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 37EvpDfgEDaoxncQ8g4ZVs4fNOxgYhss1PBkoxeaCjDlgeeB/mSus1raHapFimjdbAJ+Fz5pVWG46vNbXPRsDg==