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
- 982ff031510bf6a725cc47b0e110799c1ec155f35b3f68b7874b85065682c79d
- request
- 080af4164435bdcaa79847711ba6ce85c8a044a3324e468b1ee9b00986ec331f
- transaction
- 84ba3fb7a55a030a8bdc3675831595cf8ad8d264469298bed7a1d8314f7b8f1ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45593
the chainentry 45593
- sealed to the entry before
- f23a2914abc9ae48a15489ee3978fa27cc1b212cc86066ec1f5414b5f645daf8
- this leaf
- ce758d76f7cf577f20250e4b563a28460e6cca1f1e2da1e918d6ca9f8b46af39
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- w81BXSnLeTGtNbvSbeQH4vpne2Eshd+sM59Waoa7iGwenpIsczCCDNzgeJRoxSj3pRp+//3IQPvLEtq2S39uDQ==