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
- 3bf84850e6f02dbef9b71d01fbf8090a0fb8c17149f59739a47e163f1b255595
- request
- 1bd7d733cb9650db34ff60cbbbf22a6b53665a09f19dec396b633150463c46eb
- transaction
- d7217707d1ec4fbaf00d01a4c0bb8a8aef5568f339942929d245f2ed6fd82f36computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 76344
the chainentry 76344
- sealed to the entry before
- b6c6482800a18e8453cbaf58a4f389f5c66708e92c687b22e9c19cc31590268b
- this leaf
- 345f92c8b292cf4c13fdf479f12d9c763ba666bbda814e73f1ba7054e45edcbd
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- 3W92qL3x3CRJ4izEB2ilxml0u0/ryXoUkAFikpiuz7qu4Tlt+STHoJKzXDhx42WmXJ0XBSZjAhsx1aeOKRg1Cw==