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
- f582746690cde7b576be3e61df84cfe12e6a5b1d05d69733318e6f8f593adf74
- request
- bf0364b316ab176aab31f7f1ed11a3cf9444afc6b913d7bfc3ac23bcdbbe15db
- transaction
- 4037bbdb6182b2b3bb99ac4bc3d2f027009d7af73d0ae34bfd5005f23fe498f8computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 60993
the chainentry 60993
- sealed to the entry before
- beaa7f494c8423d366422a0732d896d23ed9fd9ad066a4ded39a37ebf0d1289c
- this leaf
- 485a57282aa0b56c017f21fa0e646b6ba5ee203a171f408e84e9079f2da0f337
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- JFESKt/54Ztv7zQqFPTRj75HpwmySMxY+1tBpsnvL0CGXGW3lEEclhcxbt5PfYXWI+GIRAdTcPA2pqwu2AkaBw==