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
- 36c5b200415b934ffc2ccc176ae5c2d8d73e562a8874cb10db06afa9bd2b5fb9
- request
- 6362403961083aec82bfb37ef3a0afd1cc81b194dd49faceb011b71030f254c6
- transaction
- b0dbf82f7fcea2fbf2ad102ff3265134ae7df82b114602921de10c0b8ac9b308computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 36190
the chainentry 36190
- sealed to the entry before
- a4617108a9c107a86ab30db3bffa493bb581fc079a21773fc9c026143870d047
- this leaf
- 11be2da0c718fd141bad234fd0a31e8b40364d7651920e8c649998e453c16437
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- UJM/VPtaem2OcSXJp5qtQew1V1UPDM5azLpSIuW+ypcnhGNshonj6oCV+Cj3S5UP4xcuK9khwUU6YrdHrOIlCg==