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
- 730c58d998bbfcb3dd3d365de4e332ad4e90bad2a59eeffe34b4436be02720e2
- request
- 550b6876af1f343ccdc6f8e97a718cc6efadd72a196ff71a5b1821a7509748f6
- transaction
- 855d9e61bc2cc0e120b6f195c4f6c470e8038c68fb7514a4e716a49fd3e9a891computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 30046
the chainentry 30046
- sealed to the entry before
- 5e195094661c1b9b537f3c9dc5f195ad063b44246dfc55cb75975408662ce87c
- this leaf
- c7db1fe63474c11cd2fa2d02011e3715555849e67d2a90dfb4fafe6454d4a1fb
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- tXNx2GjhNEaEgsmcAAGwKN1VcvYXru3nI1d2AvfxSIZNrQvdCDqxi0YJ3IJh/xNxz1DW5GjGbpXvGkpTJ1HpBQ==