SCI - Receive payments worldwide

Start accepting global payments online. - UnifiedPurse makes people want to pay you!

UnifiedPurse enables you to accept unified payments worldwide, from a single point. Providing over 80 popular payment alternatives (e.g PayPal, Bank, Perfectmoney...) to your payers, and collects your payments into a unified purse.
IMPORTANT: Before asking any question about the process flow and withdrawals, please read how it works here. We will only respond to questions that has not been already answered.
To copy customized payment snippet to be integrated on your website, please scroll down and click on "Generate HTML Snippet" button.

CMS & E-Commerce Payment Plugins


Easily integrate UnifiedPurse payment method into your CMS/E-Commerce websites using these ready-made modules for each platform.

Customized Payment Form


Please click here to login first , for these snippets to be personalized with your username!
Generate typical HTML snippets or URL to accept payments into your UnifiedPurse
(Explanations of fields are at the bottom of the page)

Advanced Options (Callback Parameters, Payment Notification/Tracking, Split Payment, Pre-trusted Transaction)

Copy any suitable one from the generated snippets and paste on your webpage/application.

Payment Snippets


SCI Parameters


The following parameters can be sent, through HTTP GET or POST request to the URL: //unifiedpurse.com/sci

Input Field Name Description Example Value
receiver Receiver's UnifiedPurse username or email a@b.com
amount Total amount to be received 1000
currency Currency can be any of BTC,LTC,ETH or any other currency that you have added for SCI by indicating the conversion rate here. 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. ab@b.com
receiver3 Third receiver's UnifiedPurse username or email. abc@b.com
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
email Payer's email abcd@b.com
country Payer's country-code NG
trust_token

Normally, if a payer that doesn't have account with unifiedpurse wants to buy crypto-currency from a exchanger on unifiedpurse in order to pay you, they will be required to register and perform KYC first;

However, if you vouch for them throug this trust_token (that you've already done KYC with them), then they will be be allowed to buy from exchanger to pay you as a single 3-way transaction without KYC

trust_token is generated by the following computation (you can implement the equivalent in any language)
$my_secret_key=hash('sha512',$my_account_password.$my_account_email);
$lowercase_concat=strtolower($firstname.$lastname.$email.$phone);
$trust_token=md5($lowercase_concat.$my_secret_key);
dkkfeiif38399f39288r8383838

More Fun-facts About ref

You can enforce a payment deadline-date for your invoice by "including" DLD-dd-mm-yyyy in the ref

(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.

If you include the word URANDOM in your 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.

Payment Verification - Instant Payment Notification (IPN)

After reciving payments via this shopping-cart interface (SCI), it is important to verify that the payment was atually made by performing the payment confirmation step. Click here to see how to verify payments