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
- acc7082931ccd6985f26e50e06c132fc7d3cfa38f8142dceb5f17de4a31ab449
- request
- 7184ef517620ebdd23ff40094423cbeeac0f55fe3af9bd6177ab720b32ab99e7
- transaction
- 3a928478ca9a41cd161e7d5909fd754c93c94f338efee4ef7d3346ea1a5db349computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 52243
the chainentry 52243
- sealed to the entry before
- 82387d5f81405a1631deaee85cab41d70a09aa885a24b17464331ec6c5758c2e
- this leaf
- 309be81e010a2c5d943e35006106437b35e0af05374e02d95c87163f2d3b9ca5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- IkRS2lSB87jRcll1bS8+Ra/jQGEXm1Va6R94BTGS9TNGB7FYxQW5Wwb+WWKtKaurX+VKiy5bpHmQ/RIvtB4UBg==