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
- 0a9d56e132cc83104e6101d5ac24f4eb25eeda51148d16d8f444177de5b263ba
- request
- 172c37fe133c34589ff22183a6a8e5a1c6c884106559786c9a4c93774522a2c9
- transaction
- 165a9b7161d7dc8dc945640b30520eaac057c03a9d72f88a0f2d933054919c58computed before submission, so a refusal has one too. this never settled.
verified in your browserentry 46974
the chainentry 46974
- sealed to the entry before
- 99820d0350baf59ad57cc084558c589a785abf4d0a5ce45c47b955344f433eae
- this leaf
- 691bafbef97d6d8ef8379698c2aecf4bdfdaca459c8fc8e805063cc77d82ab85
- signed by
- GB6LRI3NHIMJT5CFHSFAVYB4YQLQXFQF34KMQY2KS263H2J6V6EO7L2S
- signature
- ToRoQzkBzh0qBj2nqcKtbhTm3+Um+B+/F4oaYfG0S+yA9+Kd5MgsOTLeO3IBGC0IllswYJU/r7PRLPlEqn2ZBw==