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
- d25596cf9d76e82f31de623f4c85e1146519b96f82a8d8adb0e165d13403983c
- request
- c44e2bb60d03530be8296786b83647c1d07eae0fa71a709818a87b0f8a11f83e
- transaction
- 62f0c911acbc48d1eb542001ad45bccefe46f857b528927637ebcf22a9697edacomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 25244
the chainentry 25244
- sealed to the entry before
- 4905ecc8e87840525700c38b0555a679eb34f692f998d495c0e6c8c6319da125
- this leaf
- 2451095c1d39e1ea99985f02a1b11170d2aed0e5161460480b390f5e85723525
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XFIYDNWOeDo4QYOIUtiV5XVn+qwyd0AoEK/r59MqA9kZ0IUCqkff4o/n2PTGkIzjME94CC5DOYXQlzWLANSMCQ==