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
- 9fb349693e193ae184aee954e524b747b98b0c5b7eb558f087a0d87c04f5fdb8
- request
- 8c021e480f20e8386c3c7d438190e222bdf74f7dbc237ca5930f2951bb212544
- transaction
- 024eff9a5ee496abecc2be4566b52a034daa539aab56c928b4370e66c5ffc33bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 29562
the chainentry 29562
- sealed to the entry before
- bda99604a1971a5cb12cccc29f8e233693e394a944a75ec4c380094752561846
- this leaf
- f4ecd95186bf3015485a7648c3cc3b309184f352cf95a9e2bffc6f90ff82996f
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ByKBnMpLqRRNaxqLRDZzUlXMlmt+YMvH7qVx2g786I/luWHnYYgRJM/Be2iqwO+xTt3nQpeYvApXgeOeq9+GDg==