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
- 4261d10da2cc63e8a702b17a9656f18d8bada80feb636cfd3299e8b41fcba153
- request
- 45fc6e4d56b3c3fabecc4ae89bac2602da5660ed19bcb4983f3141c237aeeeae
- transaction
- 35cf7f8293ac0949ab4e37e043374f3a1978a64ddf8ba8fbb869097aded39183computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 70021
the chainentry 70021
- sealed to the entry before
- 27795fb179e657d6ed259ae2b6289ff9534fefc2a848fb05841c04dbd8acf378
- this leaf
- 387d9f5ebd113eb247527a0fc0b4882fdd9c3e8bb260cdb5da65d04d797ed60b
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- G/vSQ6fnyXDapuLRgVfowkBv3IQ+1eBH7KQCmjQ72/Gy8aT2LKClnhz/iUFbrPWhDO8rcYOdMPMHgN6fkbuwCA==