Signer Configurations

Signers
NOTE: Signer Configurations are used when you are creating Payments. For more information on how to create payment visit the documentation.
When you are creating payments in LimePay, you have to provide an Authorization Signature that is being send to the Escrow Contract. The purpose of the signature is to prove to the Escrow Contract that you (as dApp) have authorized the funding of a shopper.
LimePay SDKs are compiling and signing the signature behind the scenes, however you still have to provide the private key that will actually sign the authorization. 

There are several ways you can provide the private key:
KeyStore file
You can use encrypted keystore file:
1
const signerConfig = {
2
	encryptedWallet: {
3
		jsonWallet: keystore, // JSON keystore encrypted Wallet
4
		password: password
5
	}
6
} 
Copied!
Private Key
You can use plain private key:
1
const signerConfig = {
2
	privateKey: 'private_key_here'
3
}
Copied!
Decrypted Wallet
You can use decrypted Wallet (instance of ethers.js Wallet):
1
const signerConfig = {
2
	decryptedWallet: wallet  // Ethers decrypted wallet 
3
} 
Copied!
Mnemonic
You can use mnemonic:
1
const signerConfig = {
2
	mnemonic: {
3
		mnemonic:  'YOUR_MNEMONIC_HERE',
4
		nonEnglishLocaleWorldList:  null // Optional
5
	}
6
}
Copied!
​
​
​

LimePay SDK - Previous

Payments

Next - LimePay SDK

Errors

Last modified 2yr ago

Copy link

Contents