ON-US Payment between Wallets

SendPayment

This function debits Wallet A and credits Wallet B. Wallets are internal to Lemonway, that's the reason we call those operations "ON US" operations. You can delay this payment by X days.

How it works

SendPayment debits a wallet and credits another, of the amount you set in the input.

Your platform sends the ID of the wallet that is debited, the ID of the wallet that is credited, the amount to pay, and a comment.
Lemonway answers

XML

<SendPayment xmlns="Service_mb">
  <wlLogin>string</wlLogin>
  <wlPass>string</wlPass>
  <language>string</language>
  <version>string</version>
  <walletIp>string</walletIp>
  <walletUa>string</walletUa>
  <debitWallet>string</debitWallet>
  <creditWallet>string</creditWallet>
  <amount>string</amount>
  <message>string</message>
  <scheduledDate>string</scheduledDate>
  <privateData>string</privateData>
  <OriginTransaction>string</OriginTransaction>
  <reference>string</reference>
  <isCommission>string</isCommission>
</SendPayment>

<?xml version="1.0" encoding="utf-8"?>
<TRANS_SENDPAYMENT>
	<HPAY>
		<ID>string</ID>
		<DATE> string </DATE>
		<SEN> string </SEN>
		<REC> string </REC>
		<DEB> string </DEB>
		<CRED> string </CRED>
		<COM> string </COM>
		<MSG> string </MSG>
		<STATUS> string</STATUS>
	</HPAY>
</TRANS_SENDPAYMENT>

JSON

{   
    "wlLogin":"string",
    "wlPass":"string",
    "language":"string",
    "version":"string",
    "walletIp":"string",
    "walletUa":"string",
    "debitWallet":"string",
    "creditWallet":"string",
    "amount":"string",
    "message":"string",
    "scheduledDate":"string",
    "privateData":"string",
    "OriginTransaction":"string",
    "reference":"string",
    "isCommission":"string"
}

{  
    "TRANS_SENDPAYMENT":{  
        "HPAY":{  
            "ID":"string",
            "DATE":" string ",
            "SEN":" string ",
            "REC":" string ",
            "DEB":" string ",
            "CRED":" string ",
            "COM":" string ",
            "MSG":" string ",
            "STATUS":" string"
        }
    }
}

Request Input Description

Item	Description	Mandatory	Format	Example
debitWallet	Wallet ID to be debited	Yes	[0: 256] char	33612345678 ou taxi67
creditWallet	Wallet ID to the credit	Yes	[0: 256] char	33612345678 ou taxi67
amount	Payment amount	Yes	2 decimals	15
message	Comment for the payment	No	[0:140] char	Order number 2457765AX2
scheduledDate	If scheduledDate is set, the following rules will apply:	No	[0:10] char	yyyy/MM/dd
	scheduledDate cannot be equal to the current date, Paris time
	the payment will be inserted but not executed, the status will be pending and necessary checks will not be performed.
	at 1:00 am (CET), on [scheduledDate], the checks will be performed and the payment will be finalized.
	This feature is available only for some contracts, contact commercial service for more information.
privateData	Data with multiple fields that you can associate with payment and that you can search with GetPaymentDetails.	No	[0:5139] char	My data 1;My data 2;My data 3;;My data 5
OriginTransaction	ID of the related MoneyIn transaction	No	int	12R
reference	If a reference is set, it must be unique in terms of P2P transactions	No	[0:36] char	AF222233
isCommission	Indicate if the P2P is a partner commission or not.	No	[1] char	0
	0 or empty: simple P2P
	1: P2P commission. Put in the field OriginTransaction the transaction ID of the bank wire or cheque.

Response Output Description

Item	Description	Example
ID	Request ID	255
DATE	Request Date	10/9/2011 18:09
SEN	Debited Wallet	Pizza56
REC	Beneficiary Wallet	pizza
DEB	Amount to debit	15
CRED	Amount to credit	15
COM	Fee	0
MSG	Comment	Order number 2457765AX2
STATUS	3: success	3
	0: pending (delayed payment)