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
- 2a31286efa386954663eb889ef2c99e341cc9c8e226441024eda52eacb0fcefa
- request
- 4b400a93248e166f99a278a1d7c018754ee0d700d6a41a2056fa8e7012026f8d
- transaction
- 3eb09ab056e3628044d266213157369269b21dfcb4ecb8a3346489c30bbd919bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 68640
the chainentry 68640
- sealed to the entry before
- a89a6dd29c5da2e1345f2cb37679b9214b904a2aac568849a07a4bbee9ac1fec
- this leaf
- 4935605b48b834a54069d780e22ee5e50e96a4d990ea3446750d26e71f0337d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6q76rWWaqVoR5md1yr2EowGn9/O8S/YHcJHAMXZ7Qfl3A093HtLVjyGhLxrbYpeC7iuQ6iC9KusA6EaAmWjlDA==