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
- 9a2395399d33df5602bcfc9ec990240129a81bf500388ccbb3ff92846d740e97
- request
- 42ba2e510828ff573b8d358f56b609c53a05b4a479f2514eed57b73e4ec638d2
- transaction
- 5d527ec9ad2dbf475807d2e5b65f353e8a12a3feea00fde7dd3775ae9cc688a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51665
the chainentry 51665
- sealed to the entry before
- 65097f407dcc9f2e8d0cfefbf8fba3205132a56213606186dad696630c5d33b8
- this leaf
- a79d71babc113bb503dadb32573676e1892cb71f9122fc965057d9f83ae5da57
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /UhnMJdNOb2baEs3g9B94VVZjfqn587MGD8XlYimZ5kl8Mhc6FXVabv6zxSwNs4zhOFGZCrIinaLuEMarcfYBA==