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
- f9324ef2068c72d1beced859bee1ee841c60254ddb7d702167fb00045f7fb1f2
- request
- 96b11ab8ec7b162514b5ddb4e67f69228edd7dc092943e283318cd78e8ed8a48
- transaction
- e4fa5a24c64de9269f03ecb95adfab7f7ddc94c9180e37b895c48a01d5fe053ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 20624
the chainentry 20624
- sealed to the entry before
- c54e1c6db82b7fc0bc01f5b6baa0149e104faf5a59bbe0137e98294a63f7fea1
- this leaf
- b58010dd1d1217342e8741433e302bbc4b0c7867dad39cc8996b60a5d5c09702
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 01JybCiSWbphmKihUKr1Q9GQMrWGKn5rCcBFcOQOCOwYmVyMrwZGrOmVma1lVRB1QxMElFoHyO84La9bqGrcAw==