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
- 8b8dddc46d5e9850d5bf54ee6a8008be8fff26379c82b63007aed4040cb4eb9f
- request
- d2d31d90df946696febb62305e7ef10fe92ad4532a259868eff3b1118433b17b
- transaction
- 7903c53362f163fbc4e879593ae8cff67da4035a349a310856cf83c5a155b6e4computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 34439
the chainentry 34439
- sealed to the entry before
- cf42847921fca8a0ef64e0f889d58cd07c1c296218d09c723284a44edec651fb
- this leaf
- 6b2a27f3455f378f64123badf3672e895507633e0aba0a1f005805e7d9ccc985
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 6m77ZMw0bqedUJCT9RTiik130ApQtyzODQQhcFKrmcJ5/vMmsPMnZWjrmd3EjfHrcM4AIbafc4GjdpqxSUKYCA==