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
- 1e6347de941f3ecb76511ccbf30172a01b7726fc7868275fb6be1e14f4a19c9a
- request
- 14f610b99dbc459c73d2e1af0389f5d8dcf7267cb73bce1fe1caf702fccaf93a
- transaction
- e1f278cd3c7528cd1fc73a8cd414a968128d1ae0abba5dd595077ae12bce9b20computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 48175
the chainentry 48175
- sealed to the entry before
- 7efcaf67a18bdabb8f3ec725c1b38c9493b12f9734fe6b56213d036c865410a9
- this leaf
- ac7246f585149d5ed8c45942d4bfaa8f888a40cd201a339f8c2ef382d4b68431
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- KcVS2CEalth7hnwL94tmlBAziFSFYJphMhmdlrA0BNjM3AyljNqT8gJIB21w9OHucnTpiYA84hVGmgZTiy7LCg==