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
- b3ee9065b6d50ff8b7b396cf448c2691bc4409edd5a4a78d4844ebd0df2e7220
- request
- 1ea2d82d026100b7efba85e448b7d9e0f679f754afc57ea08c31a311ff259a82
- transaction
- c6363b9e4ad16937a4f9e34947b693df2d9216aae4feb5c3f17cc068369b05dfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 201
the chainentry 201
- sealed to the entry before
- ac65b579002608c2f6afb039911050c49630938ab11360d012c7d4849aabf094
- this leaf
- 1a8bfdaf0ee7a5986e3f23d93a74fd83f343771e6d2010018ab60124ca69159d
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2jVF0ziWQ8m/rfbthBraPOoCQ5erz2gaeju1RxasUiEYRdU8z6x9BCYh08dq+c0UZSFx6IPPFGa0MA4WnRl0BQ==