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
- 9698fbea7ce85fd67820ba9fcc887c952528ddc77f205ab0fa82646faa3571dd
- request
- d9eba87b2cc9e10f868e7afef0c955c1b508599519624cdfa767e0b9598e723a
- transaction
- 0da1979844450f93c5f3aebf8020d3f0cce082e49055f923d480e1378f870bd5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 11461
the chainentry 11461
- sealed to the entry before
- 4700e5197100529a3239a1c8efcaa15e0bf54d6ed053d438ae8cb68f81c2d743
- this leaf
- 6db6623916dd41abd2fb22f63deca475923e25c5eda852749b54f4e8eb4756c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +tqmH4k5OF0+fMXS/rul5sK/kuS4x+KGqIQyQh0iOeSjuqXpdFJHDNs9Lf84CHIaIQnXUOoJocvtHt251EEJCw==