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
- 5a3cba999a2410ccc8a4690e6cd1de065869e0ea6cad6dcc973b2e23da753dc5
- request
- 2cecbee4505effd771ab1697bd68370c5edc921c0530841782de428187961fa3
- transaction
- b325f83eb389c902cfca2a3bd97c3948d597f80179e78a3a95add2b57eadbb39computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 5401
the chainentry 5401
- sealed to the entry before
- 5f97ceba7c9f7f23f41a175e25dc4c7ca690a1340b948b259f9931eaaff3b3bb
- this leaf
- 7b4f7c789410346020470c276cef95e094d4cfac707dfa57564a065ac9676248
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- GZuvo0lQ1UqncYN72PJ4usP7ike94HH8+uE/fz6iNQ07Opexcd8Sjw/i4j32EWF6KvGfaXhVbPs6RqANr7aKCQ==