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
- b60126db56eec31413c7eee7fdb4fc015e7cd9022c62da03d3cbb94cd18dd033
- request
- 86a527de34b4ba2618105204e3e903f33f978dc9cf01b8b09caa5f27e36dd95d
- transaction
- ccee99bd7a64f72bacc6f6236ad1d67632fb93c5b57ecf1110210906a8d3c9edcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 58453
the chainentry 58453
- sealed to the entry before
- 00fc6b3a0aa01525a52cb3c8cfca9acd64abb6a3a0365e6b4c69f42bd434f5f5
- this leaf
- 44b1f026b2c9060b32a710db202d2cd00597bb50f5765ca6fb0c60a1f1a4af87
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 2zFDVA2QVw7oD9oSZDpqGEwRKPmgHVotH4c3lZ4+gzNAXdOzY4+mwXmhlX83e5+SBM5aBMONljXsCk86k5tVBg==