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
- 01a4fe74f1f21f84e3beee21116afa39ad1309028c35e7bf90c4e460ad703ae4
- request
- 4f8daa5247ec259e0cf53e9292c61f62e3ba199ea4de9cddbee25f46689ec3e3
- transaction
- b9f35d21409da47dd88e5624c3022af0180edf1bf914eaaba932c66a1127ea9fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33115
the chainentry 33115
- sealed to the entry before
- 80f32ec0b22d2895b2efbf8c81e091f17d229b145fdd9e19fc5bde31bebe9033
- this leaf
- b2d02ca7e00cd3dd8eefa9f2d7b5309a068cffde1d68ff61268d91340d9ffc19
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 8A2LLS4xpmkHDhzJNI239z6URaJakuKUkhFvY7ogaIRyT1pFQMToRaXoYbp1/pxInrrMGUVkZTP9FZ+rxpnyAg==