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
- 82fbe21a4b020cba88a82d25554e1450aabc1956c7198bb18f8f4949dd3ca826
- request
- b6adaecb5ed2ed21b3ed908d7c353824183d5ee06c98994e44204003347b0062
- transaction
- d017596fe19c0c42857042078bc9038812957a1f6e9613b05a53290b137ff30dcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 72486
the chainentry 72486
- sealed to the entry before
- c3c6a7ebeb052bbcbb903c0cc265fa2e8dab16a691e3fcc39c690d58f3243dbb
- this leaf
- 272101894a1dfb14823802a229df764bc74cd8a1f631a076136b593eb8b604c4
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- dq4esHTdn7HvIyIsKC/WfEEOq1UuacYI8OD3PAsAYNg6GRRoC7g4140Ijzds8xoqYDnZXyjN67MM7eCB/KAqCw==