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
- 81273b51f528b3278fdd6bf1ac0965d8b867b3d8352b3fb5fd913d13234c5e4a
- request
- 9655d85b673d4f7816be3999998213918c1a98a64372477ed18d4a2a328ecc88
- transaction
- 00068e9d2fbabad645189aa71f263c40515bce534c8da5bc584f882b5466d33dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55968
the chainentry 55968
- sealed to the entry before
- a76d89e3eeef45f5aaf273cde015242ca63d22d0d09b91097fa32e5544d61373
- this leaf
- d1202a112b0c27d6613a73608d2bebec8348b7cab7ca0a016e2c946ad817deff
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- NDWooe7cjWwxuBoqyiTw6RUPZxpkia5Uv19zz7Ox7iFxG4fPDCzvLS7LNKZhuv90aeHolgzwHT62Y8SPb/ryBw==