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
- f205ae2b774561874f991bd6866275713abf3acd2b7564a3d957ed2c8fd3166b
- request
- bc69305a237d700640c566e361172b800d643bc15a1d92da2542f0983adf7008
- transaction
- 4cc2913ad630396a2f77a0b6f77068773f3bc03bf0b67401959f5c6cb9576069computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 17863
the chainentry 17863
- sealed to the entry before
- ecb36f29ce52f509f28104cf6987e1466d6087d605c07accd7fe97c3df15b6cd
- this leaf
- 905a94e538dfba87b3d7dc73b99434cb285568c275a44276d6f831f5119f19a3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- XpIk5tc2flQmX890JNoRM3yVvDdjactS4ooQdL3kh4IJRUUiGEAID06vwWTeQG3mpwpXZD0v+uZ3rMfX49U9DQ==