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
- 806c247c1e66eb81340ecc88db193a91a58ec9c059b4f93d41643f21d3c17c76
- request
- c4ac9b637b20444c3a277c7cf1d4d8e15ccf046464d0e3de85045ad2a1238a2e
- transaction
- 2a699df3302ee7fa66d8874d058c6ce5ef6e50f8d2a484738327612e9e0c2509computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 28880
the chainentry 28880
- sealed to the entry before
- cffd2088036f3302cf651544bc9fb6ad69465d02d30eb587e28d227467f5ca0d
- this leaf
- 6119130a1c8e7da41f50f8589f99dc2c2a0db9589cc297b761ce9a3af5b8c526
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- wsEfjbpPRBdIGeT47KLVfcDEByLLow4/oXTNohwrigkrQNRbTLFDcq/c7B4Z457qa8sPtub1D/hFeDLHHXTMAQ==