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
- 77de7a349509297624c695d966254e0744051ebc837dc969063270db711939c7
- request
- 957ba17e42503d1f9341e741e4cbe3a50cf7a3fcdc110e7da2c3f9557d07ad69
- transaction
- 1094c068fb08c59353e71ab57d8d2bc27255a0a0e126a2974d139bf96ae27b2dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 33607
the chainentry 33607
- sealed to the entry before
- 2d74f6540ed3b99cff30736e317296f6410317c425510aacc25cbfc339ddbdd4
- this leaf
- a5bcd806a23130befe5cf595b50fc7912292f58fd66665420b8e4f2ca63b2cb6
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 88JbSti8SsVp6oxrAl3Zl/BX0SFU9f7y3lJnX3D0iwwejGzeoOQYTgkUsJ0yHquKcuPJBtgnDvNMIwepmSRADw==