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
- a0f419a913224e173d866be614c1d50168fd2f492f4ee834823d3545bf8fcf2f
- request
- b4463b55153f6c3dfbf7d08952f57d65323cce8f747148acc6cf85fcdbd52567
- transaction
- fbce2903b24a3aa0ac6f14fae30000781266c910870a29922ac9ef0dadf532b0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 56823
the chainentry 56823
- sealed to the entry before
- 7eb1dfa6e890eed69b376797ea483158ae5db7ab9f7a88562bea86b81240d357
- this leaf
- 90433d96f7e7998adc2d3c81e98559edd72554eaafbde8f7f3b237a2cb2d29d5
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BC/0BxLR2ll4A1agtNQbHTrtD9FOXA8E2tJNovvJ4M4gu6Kj0ft7mlmT6lXPlARrNxBkXb98Tbtc8FfdOC0sBw==