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
- 435477560dad5dfce889631794a7907f77f2c99dcd0f7d8b9b3b8cdca7465652
- request
- 24007bb2b113641d6376f4c9952c7fb88ce5b7938c6d16f816cce6d2eeedecc0
- transaction
- 5468853466f5837353546ea355392275872d0eed84a6a84ad2add8fdc6240068computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 55834
the chainentry 55834
- sealed to the entry before
- eb51adfbafd83965fe20221de018c0ec2f00f21df2aa24d1b9267219ad0f71eb
- this leaf
- 55f88816bc5ba2856431641e0a7a51a3fe1dd2cdcde9582f8580a27490c5a541
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- eRKJFxoo7Se5ZREd3qw5qp0En67EwfufFNN8y0URbvvePT4R4rVNaBjEbvE6VURFzhQueKNMmO7nKGDSspVOBQ==