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
- 8015db94501ffbd625d8747b34f4a1e2bf0386a9b972f30d97c050aba34a9114
- request
- 79baa7d6bdb0baf7868deca7671fadc72897de0b650a1280132d4d6fd83a3ad2
- transaction
- 799e02cb12cab2af6d722f6d3c50084c953566ca5a02f2edccc547d0efcec7bfcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 15851
the chainentry 15851
- sealed to the entry before
- e6b3ee6b160e7e010e2851bf320c252f3ebc036e2049100288ad75d3e4ea4b79
- this leaf
- a0d49724f35f68e215762a76594c280fc7899429af9fa6617eadef9285a0b064
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- +nvopvEef0AOzF1lC6cKcMVi3t9p0K+MCp7uAEv6ClYnx7mhj6FDeQI+PrlzbXtCUzK9E9h5QWyMVKgPWvmkBw==