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
- f18347dc9bb43315ea700ea97c489b4e738beef5eb77215d76876d9dadf648d7
- request
- 48abcd83d773c38ef9dfb16e223d1071dc664959d8816a633297d2b7160f08e2
- transaction
- e9bbf4dfb666cc2220c1a36b6c68d4de40af94c18995e0e8b34ac9b03e82e53ccomputed before submission, so a refusal has one too. this never settled.
verified in your browserentry 74605
the chainentry 74605
- sealed to the entry before
- 494ed59f9549ec6e6223a100ad526b69c30acb913f6379479f03923295ed7f85
- this leaf
- fee303b7da300110a55973f18add1e19cf5e71e7960dc29aa2c0edd6ba8292d8
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- BMPKfe6Ez/PyNjC2K+DNmmEfOm8OGkEv+rqq96q2L2zx5kUfUZaQca2I79Q8tO3SbP+NByUx3YgIhL0c+4qiBQ==