PSP

Payout is licensed financial institution providing innovative online payment solutions for ultimate satisfaction of any online business.

Payout banking

One of the most important things for clients is to have the business 100% under control. We offer tailor-made back office with an overview of all transactions paid on your e-shop with all the information you need for your own statistics, reports, accounting or administration of your funds 24/7 collected and displayed in your Payout account.

Payment options

We use our payment form on your e-shop with all payment methods you choose according to your needs, namelyt card payments, bank buttons, bank transfers, instant payments and withdrawals.

Payout features

Payout banking

is your back office which provides you with an overview of your payments, customers, fees and settings, and, lest we forget, you can make withdrawals from your Payout account 24/7.

Tailor-made solutions

are what we want to offer our clients when meeting their demands.. Payout always customizes the processes according to our client's needs.

Payment methods

offer various options of card processing, bank buttons, bank transfers and instant payments. The choice is yours.

Compliance

is necessary to process your transactions in accordance with all the legislation requirements. Payout is aware of this fact and, therefore, we have developed AML/KYC you can use.

Client Servis

is provided by experts ready to help anytime you need it. Payout banking has integrated its own system for direct authorized communication.

Card payment process flow

1

The customer places an online order for goods or services in the Client's e-shop.

2

Client ensures redirection of the request (order) to Payout Information System (IS). Client has integrated Company API in its e-shop.

3

Payout IS creates a “Pending” transaction on the Client's Payout account. Payout IS formats the transaction detail and secures the transaction authorization to a payment card intermediary and the transaction is redirected to an acquirer with ag request for processing.

4

The transaction is processed or rejected by the acquirer. The acquirer is in charge of all the elements of card payment processing, i.e. communication with a card issuer, card companies and additional security like 3D Secure. Payout IS changes the transaction status to "pending" in Payout account if confirmed by asynchronous API. Payout IS changes the transaction status to "processed" in case of confirmation via synchronous API. Payout IS changes the transaction status to "rejected" in the event of rejection. This means the transaction status is changed depending on the response from the API acquirer.

5

Payout IS makes the payment transaction in favor of the Client's Payout account and notifies the Client of the result of the execution

6

The Client confirms the status (transactions) of the order for the goods / services to the customer, i.e. whether it has been processed or rejected.

Bank button process flow

1

The customer places an online order for goods / services in the Client's e-shop.

2

The Client ensures redirection of the request (order) to Payout IS. Client has Integrated Company API in its e-shop.

3

Payout IS creates a “Pending” transaction on the Client's Payout account and sends an instruction to execute the payment transaction with all data to the Customer's Bank.

4

The customer is redirected to the payment interface of their bank which maintains their payment account and is asked to enter their access data to allow the bank to access the payment account and the pre-filled payment order form. The authentication method, the security level as well as the required data transfer structure are defined by the bank. The Bank sends information on the processing or rejection of the transaction to Payout IS. Payout IS changes the transaction status to "pending" in Payout account if confirmed by asynchronous API. Payout IS changes the transaction status to "processed" in case of confirmation via synchronous API. Payout IS changes the transaction status to "rejected" in the event of rejection.

5

The customer is redirected to the e-shop and the Client is notified via the API integration of the Payout IS and e-shop about the transaction result.

6

The Client confirms the status of the transaction (order) to the customer in the e-shop.

 
var https = require('https');

var options = {
'method': 'POST',
'hostname': 'ie.payout.one',
'path': '/api/v1/authorize',
'headers': {
'Content-Type': 'application/json',
'Accept': 'application/json'
}
};

var req = https.request(options, function (res) {
var chunks = [];

res.on("data", function (chunk) {
chunks.push(chunk);
});

res.on("end", function (chunk) {
var body = Buffer.concat(chunks);
console.log(body.toString());
});

res.on("error", function (error) {
console.error(error);
});
});

var postData =  "{\n\t\"client_id\": "88a6b2e4-c485-4250--b9b8ad92d41e",\n\t\"client_secret\": "4c4f4df3-d026--8c4b-98e0434c882a"\n}";

req.write(postData);

req.end();

 
require "uri"
require "net/http"

url = URI("https://ie.payout.one/api/v1/checkouts")

http = Net::HTTP.new(url.host, url.port)

request = Net::HTTP::Post.new(url)
request["Content-Type"] = "application/json"
request["Authorization"] = "Bearer SFMyNTY.g3QABBACZAEEZGF0YWEDZAAGc2lnbmVkbgYAe68kd2QB.72N3LRK5QXAvJteVRhzWsAsxipwplEsec06Gtg0uSw4
"
request["Accept"] = "application/json"
request.body = "{
"amount": 683,
"currency": "EUR",
"email": "john.doe@payout.one",
"customer": {
"first_name": "John",
"last_name": "Doe",
"note": "Good customer"
},
"external_id": "844c65d5-55a1-6530-f54e-02ddc9ce7b18",
"metadata": {
"note": "Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been."
},
"nonce": "a35fc329-6dc6-58ad-d40f-55bd981124b9",
"redirect_url": "https://payout.one/payment/redirect",
"signature": "0e82c6862a98ae7a0d1cd0b958c27b116e8c136bae899d43e8d115610c107bd3"
}"

response = http.request(request)
puts response.read_body

 
 "https://ie.payout.one/api/v1/authorize",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => "",
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 0,
CURLOPT_FOLLOWLOCATION => false,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_POSTFIELDS =>"{\n\t\"client_id\": "88a6b2e4-c485-4250--b9b8ad92d41e",\n\t\"client_secret\": "4c4f4df3-d026--8c4b-98e0434c882a"\n}",
CURLOPT_HTTPHEADER => array(
"Content-Type: application/json",
"Accept: application/json"
),
));

$response = curl_exec($curl);
$err = curl_error($curl);

curl_close($curl);

if ($err) {
echo "cURL Error #:" . $err;
} else {
echo $response;
} ?>

 
package main

import (
"fmt"
"strings"
"os"
"path/filepath"
"net/http"
"io/ioutil"
)

func main() {

url := "https://ie.payout.one/api/v1/checkouts"
method := "POST"

payload := strings.NewReader("{\n    \"amount\": 683,\n    \"currency\": \"EUR\",\n    \"customer\": {\n        \"email\": \"john.doe@payout.one\",\n        \"first_name\": \"John\",\n        \"last_name\": \"Doe\",\n        \"note\": \"Good customer\"\n    },\n    \"external_id\": \"844c65d5-55a1-6530-f54e-02ddc9ce7b18\",\n    \"metadata\": {\n        \"note\": \"Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been.\"\n    },\n    \"nonce\": \"a35fc329-6dc6-58ad-d40f-55bd981124b9\",\n    \"redirect_url\": \"https://payout.one/payment/redirect\",\n    \"signature\": \"0e82c6862a98ae7a0d1cd0b958c27b116e8c136bae899d43e8d115610c107bd3\"\n}")

client := &http.Client {
CheckRedirect: func(req *http.Request, via []*http.Request) error {
    return http.ErrUseLastResponse
},
}
req, err := http.NewRequest(method, url, payload)

if err != nil {
fmt.Println(err)
}
req.Header.Add("Content-Type", "application/json")
req.Header.Add("Authorization", "Bearer SFMyNTY.g3QABBACZAEEZGF0YWEDZAAGc2lnbmVkbgYAe68kd2QB.72N3LRK5QXAvJteVRhzWsAsxipwplEsec06Gtg0uSw4
")
req.Header.Add("Accept", "application/json")

res, err := client.Do(req)
defer res.Body.Close()
body, err := ioutil.ReadAll(res.Body)

fmt.Println(string(body))
}

...

Payout API

is based on 5 golden rules:

1. Documentation

2. Stability and consistency

3. Flexiblity

4. Security

5. Simplicity

These rules make Payout API easy to learn, easy to use, but hard to misuse.

One integration covers all yours payment methods

There is nothing more to add. Please, hit the button bellow, complete the registration and start to use Payout as a unique solution for your online business.

Message was succesfully sent!

Home

Products

Payment gateway

Software

Extra services

About us

Contact

Login

Sign up

EN

SK

PSP

Learn more

Start now

Start now

Payout banking

Payment options

Payout features

Payout banking

Tailor-made solutions

Payment methods

Compliance

Client Servis

Card payment process flow

1

2

3

4

5

6

Bank button process flow

1

2

3

4

5

6

Payout API

is based on 5 golden rules:

1. Documentation

2. Stability and consistency

3. Flexiblity

4. Security

5. Simplicity

These rules make Payout API easy to learn, easy to use, but hard to misuse.

Explore API

Try Sandbox

One integration covers all yours payment methods

There is nothing more to add. Please, hit the button bellow, complete the registration and start to use Payout as a unique solution for your online business.

Log in

We are sure we have caught your interest. Do not hesitate to contact us in case you have more questions.

Send