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
- b0b886ef805ed0002936cefcc62aad6e33f01285b08cbd5d6c618d7f8d54b582
- request
- a644304b6058608a8a392b2b6f82ed53db7d9465920942b6614ec751737020b8
- transaction
- aa805424574723f315a6aa5ad11712ff2f34a194dbba961845179a1f0923d9e0computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 2285
the chainentry 2285
- sealed to the entry before
- 066fa3c0b57f6532f49a86803c9dc5a25c08246bca23ad2d92fe0cd44d97d984
- this leaf
- d1029101cfb2f45aec5787bc93e8e84269e2e050c016af5cc57741f01d906997
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- D2T7HkMS73cRk2urHj206NhhkeBlHgaN5q3SbfOZtCP0lYQbLF5y1gTYXfWyT3etFfeCcJddoEXVa9mR/on0Ag==