Developers

The Developers section is where you would find find all of your security settings and configure integrations.

Overview

The Overview section provides a comprehensive summary of your API usage statistics. This includes key metrics such as Total Requests, Success Rate, Average Response Time, and Error Rate. Additionally, you will find detailed charts illustrating API Usage trends and HTTP Status Code distributions for further analysis.

KeyPair Settings

Generate Secondary KeyPair

The Secondary KeyPair is a critical security credential required for integrating with the AkashicPay SDK:

• When you first onboarded to AkashicPay, you should have already generated your first Secondary KeyPair

• This KeyPair is used to authenticate your integration with the AkashicPay SDK

• To refresh and receive a completely new Secondary KeyPair:

  1. Navigate to the KeyPair Settings page

  2. Click the "Refresh KeyPair" button

  3. Confirm the action when prompted

Important: There can only be one active Secondary KeyPair at a time. When you refresh your KeyPair, the previous one immediately becomes invalid and cannot be used. This means you will need to update the KeyPair credentials within your AkashicPay SDK implementation.

Callback Settings

API Secret

This API Secret is used to verify your webhook signatures. AkashicPay implements a robust security protocol for callback verification to ensure secure communication with Business Partners (BPs). When sending HTTP callbacks, AkashicPay includes a signed signature in the header using an API secret, allowing the BP to confirm the authenticity of the request. BPs can further verify the callback by sending a signed request back to AkashicPay, which then responds with another callback to confirm the verification. This multi-step process, combined with IP whitelisting—where BPs whitelist AkashicPay’s IP addresses—significantly reduces the risk of unauthorized callbacks or attacks from different IP ranges, preventing fraudulent auto-topups on the BP’s platform and ensuring a secure transaction environment.

For more information, please refer to the Secure Callback Endpoint page.

Callback URL Configuration

AkashicPay requires you to provide a callback URL to ensure smooth and efficient communication between your systems and the AkashicPay platform. This URL is essential for receiving notifications about transaction statuses, updates, and other important events related to your account.

Properly configuring the callback URL is crucial for the seamless operation of AkashicPay's services, ensuring that you stay informed and your transactions are processed efficiently.

Note: Deposit callbacks are not sent for Layer 1 deposits with a value less than 1 USDT.

AkashicPay allows you to set the following URLs:

Callback Type	Purpose
Payout Callback URL	Notifications for completed payouts
Deposit Callback URL	Notifications for completed deposits
Pending Payout Callback URL	Updates on registered but not finalized payouts
Pending Deposit Callback URL	Updates on registered but not finalized deposits
Failed Payout Callback URL	Alerts for unsuccessful payout attempts
Failed Deposit Callback URL	Alerts for unsuccessful deposit attempts

We currently support callback URLs for the following currencies: ETH, TRX, USDT (ETH), and USDT (TRX).

Note: Leaving any callback URL unselected means you will not receive notifications for that type of event. For critical operations, it's recommended to configure all relevant callbacks.

Best Practices

• Document KeyPair Changes: When refreshing your Secondary KeyPair, ensure all team members are aware of the change to prevent integration issues