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
- 2b14a656a9749874e2ed19687bbe398302cc2da72550256c290d92e4a36f757c
- request
- 151bfc1b0deedbde0a65d30014a29ba65a77c5f99256ba18cec2d8fef9c54b0b
- transaction
- 4e67eff4e55c002ecebbda245ef724ba89ab7c264ee78760edd7add01d767531computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 1023
the chainentry 1023
- sealed to the entry before
- f86cfd11cb85e1cea2e5143cdcc031c22e9c8d2253f14dbd79e312a0b3d08ed5
- this leaf
- b3c1706b6fe6b37bbcd562f79458ec99a547c1af63011487ccdab43c6fa415d3
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 1E46pFM67OaRaF2iN08minWg51juHd18vDVfBD4XzzpBn9CdFK9oElLBmCWtE9W5mOwGjciFtivH6e6uGZD8CA==