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
- 286d22b7052efaa0d6923531c1d0c81496affec28209ad110577b8f85707bb72
- request
- f51ff445c59e1e3c3647b31627218cd2c8ce99cbcc0fbec6a7eea0b4c1f76768
- transaction
- 0309dce450d779eaebee0fee3d46f51bacd093982bca83ed6ddcad47be86f515computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 45023
the chainentry 45023
- sealed to the entry before
- e6896a75492741206e7518489184632533a392a24d784dd2ada1d7c434f1cf5e
- this leaf
- 0c3da5ec6ffa905ed7e903dc863b1da69b40ee4c368df3ee0b361fb6cb3857f0
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 5py3G9aI6fJhuxfKNRotf5f9mJRS8lMXm+66s9OU0M8xKDYHJ6nRobO7u5olG18Yk3gTLEKGUwhP5lwCll8WDA==