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
- a5a29e90c38e131f83dbf5163899f36085825372c1e8fc8dc753286ce7b7c420
- request
- 9c002d645c56fa1f5b99b38f7a7a309632a524505a6e2a589acd12ac58c878ee
- transaction
- 690a5e7f8290a13ae5f174d8d73333f2af19914f5eff841b665fec57f9b0b963computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 65657
the chainentry 65657
- sealed to the entry before
- a8d4e28bd59a6be822c5820f18a9c050efc0b333d670c75a4da0ff4ba31a98de
- this leaf
- 782f53010fe12ccfc4bcec6b4d9ded421abd6a3f0e2e0bd6114bfa485ccb2972
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- lugWJBJefG6bjlCeBBkxtu8vOhEtpVzZoqDgHjEI3UEOTeLKyh7rtas91Im1lrvvGZnhfZBq/MmDx2/B6AOJBQ==