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
- 3c52672669614b09a44fb3c7d19d406a5e427f1c92aa639557e24db5c3d69570
- request
- 8a70b9a72210d19f4846ececad255de595f319a8231c3375a44e1358f37b6bca
- transaction
- b2a813ef46855179ce65d1d33f11a35879c314e36c19ae725323519828ee8d27computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6880
the chainentry 6880
- sealed to the entry before
- f1b966acb5c930329079330dcfda5591ef0dc17eed4b79ed3bb1df29d54151bd
- this leaf
- c6751136c05a35d38d66a1fc7e41d6237b93548ebbd8c9b737bae21a71e69193
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dlWTMh/U/iTY1pDHW+01arei4SdI00okRZampFWii7wO/XujMs1bMrkXq8LxW9QcX3qsY8YxhUShZbiDtziDDA==