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
- 0d8e17332c3f5061cf6566c59fc2be477d3c171a71f72e2abe4aa0176a78db1a
- request
- c0c74d900627dc79fd10410a9c9fecbcb3fea86dd66cdce881206ad54da58d8f
- transaction
- ce627cdf089831d92bef2fe2e4d21fc975fcf25fe4e07ff4c760ccb60a92ab99computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 22904
the chainentry 22904
- sealed to the entry before
- 8f10679cddbbe02f5364951350e84ad08848cc03b5d223ad755c108c689987ae
- this leaf
- 9686f96dfa8881eb5403c9d5e5409252dd8618fec364c4f03d2a3e5ec8a091ef
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- sHsPq/3xmNSs1j/N/JV2ste85pk2XZBa/CBs2bkXHJwSCMuXbXsrNgVDFNUzPpxgplVv0EkvNz0SqcFv9Th7BA==