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
- 0fabaa974fcbca14ad3d55d51211ad88de4e0760d71e91a5817f4485dc65c5ba
- request
- c883d08d3ff4c44684d6649597b55fe02df50872cc29f2323c35a8703c08355e
- transaction
- 612305d31e4d7011ba16d87cf92a9b262cdde3ebc06e1655eaa4dabd9922335dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60832
the chainentry 60832
- sealed to the entry before
- 43263bdd236b2ff2dab3af1c2071ce064aa10f4f3b3f632860ce467e04556954
- this leaf
- 92903710ce7595913011baf5280e4d82b7d7d2aad7865906339842377aa3d223
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- J8FvDjh1qJBUaEd4sFyyu34n57ZAJ4OdFmqAQX2Ii4CRg0CbH93io63G4vMQHaHeSLnSsglWDpd9ErmbUwBdAA==