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
- 14b4b51f7699ef202c4eb29238ada1c62ca1b93db75f2c660ad0f723c8f63b26
- request
- f6ed1853d1d743762093085060162b39d22defc47e86335e9dc36067f98adbf2
- transaction
- 7dc80902ad52f16f7f9dd0dca4200328d55695431f48699fa0223ecc44904c98computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 64185
the chainentry 64185
- sealed to the entry before
- c30a54b7d6733fdaf9c215b5898429881879035ddb0aa38a1f60ef3ef5fea833
- this leaf
- 97d9bbc0bba74ea58d9efffe934f314ec91527aab7d4f244da51022206b348bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 14ngyzMLcfj2cjrD+73bjMwL4Qq2wIJ5yl+U81F2+t/R3eyc6T01tl/wczgQl1cJUdlptdEEqIoBN7ywuA2oDg==