HomeGuidesAPI ReferenceStatus Page
API Reference

Signature creation

Learn how to quickly troubleshoot common signature creation issues.

Signature not match

The signature mismatch issue arises when the cryptographic signature generated by the system does not match the one expected by dLocal. This can be caused by errors in the signing process or alterations during data transmission.

Tips for resolution

  • Implement robust signature handling. Ensure proper implementation of cryptographic signature generation and verification processes.

Check signature examples code >


Invalid credentials

This issue occurs when the provided credentials (such as API keys, login, or secrets) are incorrect or outdated. It can lead to authentication failures, preventing successful integration.

Tips for resolution

  • Thoroughly check credentials. Double-check and update API keys, usernames, and passwords to ensure they are accurate, also check if the credentials belong to the environment you are testing, for example, if you try using sandbox credentials in the production environment, it will not work.
    • Check all the API keys.
    • Check if the problem is an incorrect x-date.
    • The format should be “Authorization”:”V2-HMAC-SHA256, Signature:<XXX>"".
    • Generate a test HMAC and compare it with the expected value to ensure your credentials are being used correctly.

3001 invalid credential

Tips for resolution

  • Configure initial settings. Make sure your IP has been whitelisted. Learn how to configure.
  • Check your credentials. Confirm x_login and x_trans_keys are used correctly. See more information about API credentials.
  • Verify account and environment alignment. Make sure the account matches the environment you are using. For example: If you switch the sandbox request URL to production, you should also switch the account.

For credential information, refer to the article Get your API credentials.


IPN Signature

Instant Payment Notification (IPN) signature-related issues may arise when validating and processing notifications from dLocal. If the signature verification fails, it can disrupt the flow of information about payment status and updates.

Tips for resolution

Validate IPN signatures. Implement a robust mechanism to validate IPN signatures for accurate processing of payment notifications.

Ensure consistent key handling. Maintain consistency in key handling between IPN notification generation and verification processes.


Check signature examples code >

© 2024 DLOCAL. ALL RIGHTS RESERVED

Dlocal LLP (Company Number UK OC413287) is a limited liability partnership incorporated in England and Wales. DLocal Limited (Company Registration Number C77538) is authorised by the Malta Financial Services Authority under the Financial Institutions Act for the issuance of electronic money and the provision of payment services. Dlocal Corp LLP (Company Number UK OC 424987) is registered as a Money Service Business (MSB) with Financial Crime Enforcement Network in United States of America (USA) under MSB Registration Numbers 31000193620515. Dlocal Corp LLP acts as agent of e-commerce merchants based in the USA, and collects payments from end users based in emerging markets, on behalf of the merchants.