Typical Result Of The Generated Iframe
Share this image with anyone to accept payments from them
//unifiedpurse.com/sci| Input Field Name | Description | Example Value |
|---|---|---|
| receiver | Receiver's UnifiedPurse username or email | [email protected] |
| amount | Total amount to be received | 1000 |
| currency | The currency code | BTC |
| Optional Fields | ||
| memo | Typically the payment description (maximum of 225 characters) | Purchase of XYZ products |
| ref |
Unique transaction reference (maximum of 84 characters) If not supplied, UnifiedPurse will automatically generate a unique reference. But you supply a reference that you have already used for another transaction, an error will occur. |
User:123-Product:ABC |
| notification_url | When a transaction has been completed, the transaction reference (under an HTTP POST key 'ref') will be posted to this url (even before the payer gets redirected to the success_url or cancel_url). It is then advisable to rather perform all the needed confirmation check & updates on this url |
http://example.com/payment/notification |
| success_url | After successfully making the payment, the payer will be redirected back to this url, with the payment data also forwarded in an HTTP POST request | http://example.com/payment/success |
| cancel_url | If the transaction failed to complete, the payer will be redirected back to this url, with the payment data also forwarded in an HTTP POST request | http://example.com/payment/cancel |
|
Split Payment Support
NB: all notifications and actions will only be applicable to the primary(first) reciever. Others can only see the effect on their balances and transaction history.
|
||
| receiver2 | Second receiver's UnifiedPurse username or email. | [email protected] |
| receiver3 | Third receiver's UnifiedPurse username or email. | [email protected] |
| sf | The sharing formula, indicating what percentage of the total amount received will be remitted to receiver,receiver2 and receiver3. This must sum-up to 100 | 50-30-20 |
Trusted Payer Priviledge (for 3-way payment support)If you supply trust-token, all the following parameters becomes compulsory
|
||
| firstname | Payer's firstname | John |
| lastname | Payer's Lstname | Doe |
| phone | Payer's phone | 2348012345678 |
| Payer's email | [email protected] | |
| country | Payer's country-code | NG |
| trust_token |
trust_token is generated by the following computation (you can implement the equivalent in any language) NB: Your secret key can be found on the account security page
$lowercase_concat=strtolower($firstname.$lastname.$email.$phone);
|
dkkfeiif38399f39288r8383838 |
|
Preliminary Response Object Properties
Properties of the
response parameter of onDone javascript callback function.
|
||
| ref | The custom transaction ref |
User:123-Product:ABC |
| status | Current transaction status. For security, please validate this status from UnifiedPurse server. | 1 |
| payment_method | Can be any of bitcoin, litecoin, ethereum, tether, tethertrc20, accesspay, alipay, firstpay, international_wire_swift, interswitch_paydirect, interswitch_webpay, national_bank_transfer, payeer, paypal, paystack, perfectmoney, quickteller, rave, remita, stanbic_bluepay, stripe, twocheckout, third_party_remittance, voguepay, western_union, zenith_globalpay, bitcoin, litecoin, ethereum, tether, tethertrc20 | bitcoin |
| payment_method_label | E.g The Bitcoin Address, or Perfectmoney account to which the payment was received (where applicable) | 3K8xKqWY4Jjc2D57CeKhwVZiindMifoi1m |
refref
(Where dd-mm-yyyy represents the day,month and year). Examples: Product003-Customer-71-DLD-31-01-2020, or even with Time (in 24 hours format), Example: Product003-Customer-71-DLD-31-01-2020T16:30. The second exaple means that anyone will not be able to make payment with Product003-Customer-71-DLD-31-01-2020T16:30 as reference, after 4:30pm, of 31st January, 2020.
ref, that word with be automatically replaced by a random numerical value here
This may be useful when you want to indicate reference code in the transaction, without having to be generating the required unique value from your sever. Example: when your ref is Prod-xyz-URANDOM it will be changed to something like Prod-xyz-9876543212 here before the payment being made.
After receiving payments via this shopping-cart interface (SCI), it is important to verify that the payment was actually made by performing the payment confirmation step. Click here to see how to verify payments
Import manage and track your transaction history from you own webpage or admin portal, by pasting a snippet.