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
- ea871627968f276c67d8493c80d87223e652f7813b1b753db77c8e4b5bdee0af
- request
- 1506352f5ed3ac9c3c7432735c98ff5b4a1bd7bb2c5292cd8081f3bb2f5ff323
- transaction
- b33503511bee42646034424f3601c700ee361782bb894a873016e15e3cef5221computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62523
the chainentry 62523
- sealed to the entry before
- 23ca8e6d9aba8e87e627a503778bc3b850dcc5ef73c80cf8e0282d53d750b0bf
- this leaf
- a8824cb663fc569d4b606d7a797d0278e60cf483ef771301837478eecb555c44
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 4wi8GiVIw/4fpv5HsLhEFF6HUtNy6Gtr1akCRRg8LmkTYe6W3iUX2y72IOwq4o02gYw7hriHNsFFIAYtC5KnDw==