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
- 0202fab37235c8e7a2da4d47237ea3f980d8eda5568f30be5793467a580c679b
- request
- f45cbe076b3277687788e5f26c71166667ec10551047fe4ebc11b9ba430b6488
- transaction
- ca30de6cb644d8834e3d3d19c3072257495464171f3fd46f038322492dcda3c1computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 42516
the chainentry 42516
- sealed to the entry before
- 5060f91b06847c2fa5677a7ff23ebb618f12e5133c6facab163b85a6d6d8079e
- this leaf
- e8b627f4b1254cbe1e8b1f0b1b9f6ac706282075b94f318294efe106bdc3d839
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /eZESM26v/An5Z1Ph8u6rVHkuxSV1UTmAWmeI/I30pM8GmAS9WmpcET7N5eJzlmFGWAOT/P0rATWoUJK+nScDg==