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
- 81dfdd7b4ec6afdedeb48d034dadfcb32cfe8a169019c47334324f27ae347ac6
- request
- d42b342ab89310b065825107bd0410f612d16b660c1cb74b4f3449012d7d5410
- transaction
- 380170fef354bba1c536a31062a312aedd94d20cfa9804ebd87f3663c562829ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34471
the chainentry 34471
- sealed to the entry before
- 3892bdedb0773bd067a52268df4ea270e058908604b0b4f6d1cc30b41f48a231
- this leaf
- 104afdbd4b3a2643533056dcf3d93be5f087ec90cefbe623863ebfc8468ff232
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- kBlKLxebyYdzD7T36iwMxsS2UGEpI8t7iKZAW1wTUS64ryab6V2JEDT2U2fekEKPcM8CDV/yNh3WPN2lJB4zCA==