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
- 3742b716045d5825d2a0e0028ec0795093b15f4f0bc8009452aea97cedc3f7ad
- request
- b219370c91f207480b65a222997db7c64eda540c57ed3cbdb069ae5159571dd1
- transaction
- 6c5f0b9416b5092d3ece84e9948de0fd35f793b941517d6672b43ef99a49461bcomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2550
the chainentry 2550
- sealed to the entry before
- ee371dcf90352c5f472ee8f2532d9b034f1e9bdce1d50d2c3d90c50895c8eae5
- this leaf
- 06f53d84879fe4d95f345c88cc87370421944ba3062318eda34543af165017d7
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- SgJPrFmDMl6a7pqTmICWjgxYdJ4zz8iCui0Hz8KB5+H9Dg6gE5PBhjXJ+KvUkrVANejys0RpF+xGHBskoSv9Cg==