Getting Started for Partner

This page describes how a partner authenticates on Intrapay

Onboarding on the IPPA for Partners is a "server-to-server" communication. Below is the description of how to authenticate with our endpoints.

PUBLIC KEY - pk_partner_xxx

Your public key will be added to the authorization header as a bearer token when making a request to our System.

SECRET KEY OF MERCHANT AND PARTNER - sk_merchant_xxx + sk_partner_xxx

The secret key of the merchant and the secret key of the partner (for example, concat string:- [sk_merchant_xxx+''+sk_partner_xxx] ) is used to generate the digital signature that is attached to the request body when making the following request:

• 1. Create an order on Intraypay by partner

• 2. Send Order Notification to Partner Order Notification URL

DIGITAL SIGNATURE & ENCRYPTION

SHA-512 is the encryption algorithm used; signed with the SECRET KEY(s)- Partner and merchant for all requests body on collection orders .

Also, note that the signature key in the request body is ignored during the signing of the request body

Digital signatures are compared as an integrity test. You compare it when we post callback to you and we compare when you create an order. what is compared is the signed body without the signature field

Partner Onboarding Endpoints

Please call this endpoint once. To add extra currency go to you intrapay dashboad and add subaccount for more currencies.

This endpoint is to register a partner

POST https://exchanger-api.fuspay.finance/api/v1/no-auth/PartnerP2P/OnboardPartner.

Partner's Public, Secret Keys, and partners ID will be sent to Partner email as a one-time link.

Headers

Name	Type	Description
Content-Type*	String	application/json

Request Body

Name	Type	Description
partner_code*	String	a code signifying the partner
email*	String	email of the partner

200: OK

Example request- Code.

Nodejs

const fetch = require('node-fetch');

fetch("https://exchanger-api.fuspay.finance/api/v1/no-auth/PartnerP2P/OnboardPartner", {
  "method": "POST",
  "headers": {
    "Content-Type": "application/json",
    "cookie": "connect.sid=s%253AoNBPv4ez8npeuKVKlS9KwX_1Dshiamlf.n8opjPuoF3XsU%252Be0VTLMUe6xzeAXmpCfQrpW9KW1KDs"
  },
  "body": {
    "partner_code": "Binance",
    "email": "[e-mail]"
  }
})
  .then(response => console.log(response))
  .catch(err => console.error(err));

cURL

curl "https://exchanger-api.fuspay.finance/api/v1/no-auth/PartnerP2P/OnboardPartner" \
  -H 'Content-Type: application/json' \
  -X POST \
  -b 'connect.sid'='s%3AoNBPv4ez8npeuKVKlS9KwX_1Dshiamlf.n8opjPuoF3XsU%2Be0VTLMUe6xzeAXmpCfQrpW9KW1KDs' \
  -d '{
  "partner_code": "Binance",
  "email": "[e-mail]"
}' 

After onboarding on the partner onboarding endpoint, you have to provide the IPs for your system. As the IPs need to whitelisted on our system.

Regenerate Partners Pub/Priv Keys

This endpoint is used by partners to regenerate their keys

POST https://exchanger-api.fuspay.finance/api/v1/no-auth/PartnerP2P/ResetPartnerKeys/

A One time reset link is sent to the partner email address to regenerate the keys. Your Partner Id remains the Same only your pub and priv key changes

Old keys becomes invalid

Headers

Name	Type	Description
Content-type*	String	application/json

Request Body

Name	Type	Description
email*	String	[e-mail]
partner_code*	String	the partner code used on partner onboarding

200: OK

Example Request- Code

Node

const fetch = require('node-fetch');

fetch("https://exchanger-api.fuspay.finance/api/v1/no-auth/PartnerP2P/GenKeysForPartner", {
  "method": "POST",
  "headers": {
    "Content-Type": "application/json",
  },
  "body": {
    "email": "[e-mail]",
    "partner_code":"",
  }
})
  .then(response => console.log(response))
  .catch(err => console.error(err));