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
- 9f060880308818f41a0859b6eae5445f6908f6f844ab4e331b2b3293ba18fbe5
- request
- e6158c1966fad1d0937099c4f1bcc79014bac39e08fd6f482fe571cb2bf7ebbd
- transaction
- b70b7ee3bbbd088e088624381348845d5847785869c34a0e5b675869f1eead13computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 24099
the chainentry 24099
- sealed to the entry before
- f79330804176ee959457f21a8e9b5cf93acb468eb5b78bc7fd78ef0367d4a80f
- this leaf
- fcf44f6e4ae840bc7b1b53f5b454128a448d975d54f1e142de59342e911938e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h+O5drKnBE3G+6Tdpb6MNxdqzUTNB8U+HQla5Uz1UPsNIAgGtnk7JzsNp4WCY5npjey4Gqkf7TN3QvJXhFMdAg==