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
- 2bcb8168ebe7d9d6ce341c44dbc32f4e48869fbf941c67a431242f87433c22fe
- request
- 0c31b438fe228d743b56a05873063eecebafde046b029e27b2be4dbc3de71748
- transaction
- b210ef8aeed2f25762eab81ae9c002793330183dd43d2e57d9057d7df2d85e01computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 6912
the chainentry 6912
- sealed to the entry before
- 3bb984219049f1956f1db3f512f8b1536a4a89916ebe984091b8215f7f7cd1fd
- this leaf
- c6db050978c19b90aa99944dc77262ac888fbd7669adc4b43e8546f89ea2e3bd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UCJ15G7RFIfyDTGW9MkysxYAmx1o77AvcIalJgT3rg/MFMP2Y9RKwgk9WQqsVEZCN6dT2F+XFJCnlToqEubrCg==