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
- 070bcf0dcaa42f46fd010dda537bf6fbfacbbe49fc1883a1658aeeb98b301426
- request
- 04dd076481625a56a132a6d02cad22ea583dd80cd6cdfa49668410138da3dc6f
- transaction
- 75d9329c0e33484bc70363f776e96ec26d4aed69aa408192b21d5a9ed5c727c5computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2726
the chainentry 2726
- sealed to the entry before
- d12f3d9e71a61436b36c3b017c68e0d6768200ef0a1aea2b2e1ce790ba9f6562
- this leaf
- 397c2aeffbd6d388f700d9260401f226c956e13d2947ab7a24c2f360ee40b3e2
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- LQzVCgqD+USoh4puDpbYCyVgHLjxY96cPe6Kc02xihkA53ehe5LQBockpLORyYzbqEA+JaMjFB2t4kC16ProAQ==