Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
conceal-pay [2019/09/01 03:54] – [Advanced payment with Instant Payment Notification] taegus | conceal-pay [2020/02/24 19:53] (current) – boot2thrill | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | Conceal Pay is a product of **Conceal.cloud** and offers two extra ways of receiving payments in CCX | + | Conceal.Pay makes it simple for businesses and people to receive payments on the Conceal.Network. Conceal.Pay is seamlessly integrated with the Conceal.Cloud for absolute ease of use. You can easily create URLs with a simple web page where customers and friends can send you payments. Conceal.Pay makes it trivial for you or your business to receive payments online, fast. |
+ | |||
+ | Conceal Pay is a product of [[https:// | ||
====Simple payment request / donation ==== | ====Simple payment request / donation ==== | ||
- | First one is a simple HTML widget that allows users to place a button on their website or just share a link and get paid. The amount can be predefined as well as a description of the payment/ | + | The first method |
- | Note that for this to work, both parties need to own a conceal | + | Note that for this to work, both parties need to own a [[https://conceal.cloud/ |
- | **Step by step guide** | + | **__Step |
First click on Conceal Pay link in conceal.cloud, | First click on Conceal Pay link in conceal.cloud, | ||
Line 53: | Line 55: | ||
Once all the fields are set, you will receive the URL that you need to use in your website/ | Once all the fields are set, you will receive the URL that you need to use in your website/ | ||
- | **Step by step guide** | + | **__Step |
For people wanting to integrate payments with conceal.pay system into their e-commerce or service’s website, we have a very functional feature to offer. This requires some technical knowledge, ideally made by the person who is a web developer. | For people wanting to integrate payments with conceal.pay system into their e-commerce or service’s website, we have a very functional feature to offer. This requires some technical knowledge, ideally made by the person who is a web developer. | ||
+ | |||
First thing that you have to do is to implement a callback endpoint on your e-commerce platform to receive payment confirmation data from our conceal.cloud side. This should be non-public URL, ideally behind some API1 key or similar. | First thing that you have to do is to implement a callback endpoint on your e-commerce platform to receive payment confirmation data from our conceal.cloud side. This should be non-public URL, ideally behind some API1 key or similar. | ||
+ | |||
For example if you website is www.my-supercool-store.tld, | For example if you website is www.my-supercool-store.tld, | ||
+ | |||
Second thing you have to be able to provide are both success/ | Second thing you have to be able to provide are both success/ | ||
+ | |||
Once you have this information, | Once you have this information, | ||
+ | {{ : | ||
+ | |||
+ | **Name of the business** is what will show up on the title (similar to how paypal works) | ||
+ | |||
+ | **Callback URL** is what was described above, as well as success/ | ||
+ | |||
+ | **Nr. of retries** is the amount of times our system will try to reach your callback URL in case of system errors until giving up. | ||
+ | |||
+ | **Nr. of confirmations** is the amount of confirmations that transaction needs to have before we trigger a call to your callback endpoint. | ||
+ | |||
+ | Once you click update, you will get a unique URL in the bottom that you need to integrate into your website. This is the url that you will redirect your user to after he selects CCX as a payment method. Once he has paid or cancelled, we redirect back respectively to your success or failure urls. | ||
+ | |||
+ | **For example:** | ||
+ | |||
+ | https:// | ||
+ | |||
+ | This is an example URL generated by your system. Your e-commerce platform has to use this url but also has to adapt the AMOUNT and REF (reference) fields. | ||
+ | |||
+ | Let’s say the user created an order in your system and selects CCX to pay. Your system already has the order inside your database with some ID like for example order-12345 and amount to be paid like 100CCX. Before you redirect to conceal.pay link, it needs to be modified like this: | ||
+ | |||
+ | https:// | ||
+ | |||
+ | What user will see is this: | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | That's it. Once the payment is done, user is redirected to a success URL you provided. After N amount of confirmations, | ||
+ | |||
+ | <code javascript> | ||
+ | [ | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ' | ||
+ | ] | ||
+ | </ | ||
+ | |||
+ | This will be a POST method call with JSON body as data. Your e-commerce platform will have to know how to handle this. | ||