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
- 14d4c4a560f147695d49fd07be3f29c4e7258aecbff0ead51c935766ee93bb9f
- request
- 010c3252a8e6806022c43e3c20787c750975d28b7166a995f9056d6528715db7
- transaction
- e6057b0944d7985e8f0c729f29df3837fc6ef89ff4f4453e76ad1611c30fb265computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 73215
the chainentry 73215
- sealed to the entry before
- ab9367c63d5ae6b27ddbd3927ec8911e08b7d6784598efe2763387f65fc7d354
- this leaf
- 656270ae9c5936828925e8d311db3405aacbde5a1b54980d3ded529e3e4e6dde
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 772cLok7mzOeuwzokMgskR1W3vduv2eRf3kCLDmHweQygOA+dGo8IztVxD1ug1L+9sAVYFysxualM2QO9IV3Bw==