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
- 94cdde15223cf69e95993a4a9fa273a0658f127b2734cddb8c7d78406dd44358
- request
- f4d5527ad940f73c17cd84cc19caf460a9226940a963cccf0cffc1c3557764f6
- transaction
- 47608645edd1c2151a076c671db8cb3292507ffba77809811db83d7b92d12c70computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22156
the chainentry 22156
- sealed to the entry before
- 25e9c1ed574fe247ee293d6061b62b24fd36dfa206e6fd67008c00af41318310
- this leaf
- 2dd847a8ba8013ccfaf30444b686c277b35a2fba1296d3166d61cbe9da15a851
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- PfpPeymadFiFUPq2Mo268a30E52A8Hqv71JmdxKoadFnQ/B1mUoP/G7v/2F/KX+slGvZimTT3hWtw9xZukZZDg==