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
- 38707875386c935a6ac2d3483911099ffa1cfa5a71d6488c9d2555a6531a33b0
- request
- ca111a7bd446e147418cab22c574bab5c953469706331ec2c63b154615920810
- transaction
- 1e74876af25c2967b5d966528a8458e68d149d5372e8d85ad44d1508d80e78a3computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22189
the chainentry 22189
- sealed to the entry before
- ce074a5f074a14983dd34da147fb4ef3d181a5e0418dfa9bc4128f33c23606cf
- this leaf
- b89b5c350d1bd6f12c0a2acf9171315beff8e06bd4c3232606b63fb7d43d5c90
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XEmJbGZEqT2TgEGpcPioZctKC5xeSeN8iiJc49wQ3dVZoC06rt1SI6kpFe+B0+cF+NefhCdo8D64q7q5AnACDQ==