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
- 20aefd9d02406263461bf40a80e0fb5db7d93e594b555b91295bfbad2fbeae08
- request
- 4c595f9074b695d63e14262c5e50fa134688073b8b74af9d1bfe89473ead20af
- transaction
- c901a6831c002797e17baec736d9e74d6a2ca1fe219fc3277d27a3e1b1353441computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55334
the chainentry 55334
- sealed to the entry before
- 9f36300f989fa86235de434bf25fd20c4d104052f0d31c69daf78bd63762f806
- this leaf
- e7192eba33f06f00c2a85394ea1e695517e5bb479c4b85fab163490e45d5ecbb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- hXmOB8JwqcubzA7UQT9gd4/zeWj1iBHV/C/F/rAGqTwme8cxkCliEyQy0ybZSPRylsHNpkWBYUxX6b3gvU9DBw==