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
- 9850e9487aaeccd90c6325977ba8c1deb1c1ad651ddba37a56079abb6e56403f
- request
- 85d0217deac5739bfb50c674cb771837b0d31eb0a9e7d66e29175551a7f8cbcb
- transaction
- 3ea7694e675215bff7982f8b9da3da04cb224cafdd186350473970c261e8cc9fcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76092
the chainentry 76092
- sealed to the entry before
- 240b4836fe15cadff04ba4762fd6eb8163f2575343bd49a0b2332c749d89a2bc
- this leaf
- 4fa17424f4e7f16f888a90ca033863854cc88014def3b8906051c8d571cfa370
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- /KGQIUxLKy/pr94OeXHsm3cOHSJiMxnE2LtGCQgtPZIqjKaMkO/xFIbq85Zds7f+Nw0b5u5kUkzdG4cWqz2NCA==