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
- 9338b2e4ce0320f6735d97b4827e7d17cef8f161ddb70e831bac4f91e6eeb6c5
- request
- bf6d1b01ef1c22897fdbe75b2321704b7d20280255f4631c644d9a4fce744cf1
- transaction
- bf33adab973ad72cdbcb1b7a6d536c1c426ed4516eaebbea7d41a0ef253efcb0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70072
the chainentry 70072
- sealed to the entry before
- e5784116a845c921a12c1ee5e6b8c8195992046059aa9a3e09c68cc87de06cf9
- this leaf
- cb64abc9c379d8703351184e3522b4a0d93a72c804b04ecb8901500a94c97c04
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- nb8VfQJmxPuSB+4+kO8IrSjZxnVk3uk+1ao9TO0DVEFS3izENrwkd/MmkERo6ZTWOteXIlLN9Xo4GggPPwKUDQ==