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
- aab31043f365970c78a17962029e2c3379893e5ec78e884b749fdeb8e2052485
- request
- a84098baa3eabebcca168011676bb7a2e68f86e36d227a2749c3c9f895ad9563
- transaction
- a2d1e1adb869ba70309c6ec98dfc9227eb472770fb90ae3fc3306cbd3fe52d86computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23158
the chainentry 23158
- sealed to the entry before
- 1d17a1da49d76c78d9ec24f1bcca6c6fa59d5fe23304b226c463044780b8c6f0
- this leaf
- 66c325eef7d06c9a134e0cfeacb89e07357478dcd424f11642a9e6742ddd9385
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- RX0MYHQTRxZZ1W47yQGF59xczWYoBKLf30aSuPcqzlvjLc48dQDiVefKo8tAOpchvX+PllW16TlAuVWJYnEXBg==