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
- ba9fd6956680d0cd22eafc5bc6a8945c4eca3bf7d33fa28ba199f1b9f5696991
- request
- 05d0cc33f33285d2b89ec8742457a8419f83f6415052645ddc83c7b5b29abfbe
- transaction
- fb003ffc70ed4e379461db67b85d3b33140702bec978fb08715b65d315f8abaecomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 4400
the chainentry 4400
- sealed to the entry before
- 89361b34d937b0c0066f3a7cf353594938b4b223ba9df2469d0aa9b3286dc928
- this leaf
- 7187467f3f46b1db8fcddc3fae72d64897309fb6efd78bfa7cbc1ecf98ad9d64
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- oRVHmBoxrfHWzvBZTdAG+PIUNIhnMpdw+dT/95eFBK8+MwY0dfuOxpcSwnECsPVFjhvGDjIKrGojnESstRhxAw==