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
- b676ef0c46d59f78742d41351d2e6b4ccafe27667759abbd933b7a92627126fe
- request
- a7a0d90caeda9a7d82eb7a1792b45e2a195a4806dcd35130de1ef122b399e3f0
- transaction
- e0530f781dcb612b1b1e46339ed48d2664be100477cf8c3bbde335720d8dc164computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 62147
the chainentry 62147
- sealed to the entry before
- 0c7d7ca9d10514b5eef4fe48072290276dec5aebb9165ff659e04b3bb98cc0f0
- this leaf
- dd5db950296e8ebbfe0fc9c0158f3e4868cb3bdcf28ea1ca5c17bf45c4fe1016
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- toSZH18BMv7hwJHqqHKx9FM/wUI8KAEsS22UHRkaswbqvJXlkff6rWgFIOY2CoFrBT/uDD4MZGPh2yOxZzHwCg==