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
- c90321e8b233fcdf5df25023075a1333d6258516d38e0daa885baedf3f78f8ff
- request
- 6c787303af1e282ab76e6c8eed4445ea13c3bdef4421322848ae98c68296c37b
- transaction
- d22241b9e87683ef05348476e87cc35b7a22dac0bb05c0fe5330977eec70af9ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 35462
the chainentry 35462
- sealed to the entry before
- 918fff4eabb42289a6c27273beb463c98e94b5635dfc2ce5083b6dfc84ce6ade
- this leaf
- 6c71772ae8c42c3e5e9525ff454a67ff3f42eb7f68f510fb6e00593586c4b6cd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- h6tgHwNKCZEtUWkS+OvI77jQdluZuFD1BGPKnu+7WfMJLR724H+C1/mhOYBTweYyGoWfIRAQf18JxvZuG4U6Cw==