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
- 6dc3b8feaf9900631024a03381817019c9e095952b83a5e9ad6c799097558538
- request
- ea11214b2f196bbc689ebba00d7e315e3a164d4f65b58bd704ae76d1eb81592e
- transaction
- 754f963b290b91889d6de5e71e43899f55e2d708e7a2063e8edd591067f5a576computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 23256
the chainentry 23256
- sealed to the entry before
- 0db2fd3c5c4faf687e29b2c2c5f42ba8d7db8e3c897bacdd23e8b69cdaa05a89
- this leaf
- df8a0a02faea6035381dec8cb44d59b715b668f59f7a030f8293f59768bdd6ee
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- EQPSuS9jgwM5K8T5BNjkOK1M168WftJ4Zmo7PQ4XGXvnh741tGKRplflZ+gd/JQp5dyFRwVA+e47cCiMOMGrCw==