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
- 934135ddde9825d06a2ea0129064f718ed3f21ceb9018305556a31f7c2f6eaf2
- request
- 40284930b3854c62b070f33dba675298b25bf6e50ab2408ad747600281d39c8d
- transaction
- 0af58e13ac0f51eb27f4e6c6b46cb26fca71bf13beacc0a0d241acae5cc4c40ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 9802
the chainentry 9802
- sealed to the entry before
- 01b4797bcaf16912877150f9f043b86b929aa53242939afbea211b5783239a43
- this leaf
- 5368426fb305c34c7b58fe1ce3667e5fbdd670d4d3876554570a4ceab43cad8a
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- x5DfiLOJCsfzNvWr6EXYwJbjvOrcMZkyx2QTpfgPUN+8oQMqh2K54WdaOY8fka90yZ0k0tOt0uIjZXH4z/EnBA==