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
- f8f00a6c1feac3ec4039aed663190b0afe9cd9c27bc6d782a6e0ff531a8ee968
- request
- 2166719c0173fe35572b4ecf03af02eff22ddf434689141f21147ca101d6ed69
- transaction
- 4e6ca4cb2be20769ebef291f6352f9a4634e904704b78adbcf1109fd8774a74acomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 51098
the chainentry 51098
- sealed to the entry before
- d61e6a8ccec3ffa33372206dbe35c8fc3e9bb9f0325fd4a31415ef35c1e9a5ff
- this leaf
- 08be81653c3f2823dbd2b9ad03bb1c24acf7a2853171228acb41bb40f07ad15c
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- Q/h3YGu5se5IH8FH37KElrzsrIlSDmfVVSw83QXrUEwkjE4R1Ol2co2E4oclI3dHJlQipoGELsg1hXiZZEQZBA==