simpay-api (1.0.0)

Download OpenAPI specification:Download

SMS

Service List

Retrieve a list of available SMS services on the account

Authorizations:
bearerAuth

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Retrieve Service Information

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Verify Code Validity

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Request Body schema: application/json
required
One of
code
required
string (SmsCode) [ 6 .. 6 ] ^[A-Z0-9]{6}$

Code from the SMS message

number
required
integer (ServiceNumbers)
Enum: 7055 7155 7255 7355 7455 7555 7636 77464 78464 7936 91055 91155 91455 91664 91955 92055 92555

Number for sending SMS messages

Responses

Request samples

Content type
application/json
Example
{
  • "code": "AB12D6",
  • "number": 7055
}

Response samples

Content type
application/json
Example
{
  • "success": true,
  • "data": {
    }
}

Retrieve Transaction List

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Retrieve Transaction Information

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

transactionId
required
integer

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Retrieve Service Numbers Information

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Retrieve Service Number Information

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

number
required
integer

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Retrieve All Available Numbers

Authorizations:
bearerAuth

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Retrieve Number Information

Authorizations:
bearerAuth
path Parameters
number
required
integer

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

DirectBilling

Signature

Calculating the signature for receiving notifications

Generate the signature by concatenating all received parameters (except signature) in the order from the available table above, separating them with a separator |, and adding the key available in the client panel for the service at the end.
Hashing must be done using sha256.
Example:
dc261d4f-31ef-4728-bfd6-97bbe2a5ef0a|e14f8074|transaction_db_payed|11.07|13.67|5.00|https://www.simpay.pl/complete|https://www.simpay.pl/failure|test|123123123|1|key

Receiving transaction information Webhook

POST

Request Body schema: application/json
id
required
string <uuid> (TransactionId) = 36 characters ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]...

Id transakcji

serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

status
required
string (directbillingTransactionStatus)
Enum: "transaction_db_new" "transaction_db_confirmed" "transaction_db_payed" "transaction_db_rejected"

Transaction status

required
object

Transaction amounts

object
control
string
number_from
required
string

Phone number from which the transaction was conducted

provider
required
integer
signature
required
string

Signature of the notification Read how to generate the signature

Responses

Request samples

Content type
application/json
{
  • "id": "dc261d4f-31ef-4728-bfd6-97bbe2a5ef0a",
  • "serviceId": "e14f8074",
  • "status": "transaction_db_payed",
  • "values": {
    },
  • "returns": {},
  • "number_from": "48123123123",
  • "provider": 1,
  • "signature": "a3116cf4f1e960223c2cc3088bf387278b6675255209bdeaf96a2f316a2fadc1"
}

Response samples

Content type
text/plain
OK

Retrieve Service List

Authorizations:
bearerAuth

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Retrieve Service Information

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Calculate Commission

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

query Parameters
amount
required
number <float>

The amount you want to receive "net"

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Retrieve Transaction List

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

query Parameters
filter[status]
string (directbillingTransactionStatus)
Enum: "transaction_db_new" "transaction_db_confirmed" "transaction_db_payed" "transaction_db_rejected"

Transaction status

filter[phoneNumber]
string
Example: filter[phoneNumber]=48123123123

Phone number from which the transaction was conducted

filter[control]
string

Control field from the partner's system

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Generate Transaction

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Request Body schema: application/json
One of
amount
required
number <float>

Transaction amount

amountType
string
Default: "gross"
Enum: "required" "net" "gross"

Type of transaction amount

  • required - flat amount the partner wants to receive, the final amount to be paid will be visible at the gate and depends on the operator
  • net - net amount
  • gross - gross amount
description
string <= 128

Description of the transaction visible at the payment gate

control
string <= 128

Parameter for use by the partner to identify the transaction

object

URLs to redirect the client after the transaction

phoneNumber
string

Enforced phone number

steamid
string <steamId64>

Optional field (steamid64)

Responses

Request samples

Content type
application/json
Example
{}

Response samples

Content type
application/json
{}

Retrieve Transaction Information

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

transactionId
required
string <uuid> (TransactionId) = 36 characters ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]...

Id transakcji

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Online Payments

Signature

Calculating the signature for receiving notifications

Generate the signature by concatenating all received parameters (except signature) in the order from the available table above, separating them with a separator |, and adding the key available in the client panel for the service at the end.
Hashing must be done using sha256.
Example:
dc261d4f-31ef-4728-bfd6-97bbe2a5ef0a|e14f8074|transaction_paid|10|PLN|9.9|88643ada8857f25a1f391395f922f7db|blik|production|key

Receiving transaction information Webhook

POST

Request Body schema: application/json
id
required
string <uuid> (TransactionId) = 36 characters ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]...

Id transakcji

service_id
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

status
required
string (paymentTransactionStatus)
Enum: "transaction_new" "transaction_confirmed" "transaction_generated" "transaction_paid" "transaction_failed" "transaction_expired" "transaction_canceled"

Transaction status

required
object

Billing object

control
string

Field for use by the partner

channel
required
string

Payment channel

environment
required
string
Enum: "production" "test"
signature
required
string

Signature of the notification Read how to generate the signature
The partner is required to verify the signature upon receiving the notification. You can also make a request to the endpoint Retrieve transaction details

Responses

Request samples

Content type
application/json
{
  • "id": "dc261d4f-31ef-4728-bfd6-97bbe2a5ef0a",
  • "service_id": "e14f8074",
  • "status": "transaction_paid",
  • "amount": {
    },
  • "control": "88643ada8857f25a1f391395f922f7db",
  • "channel": "blik",
  • "environment": "production",
  • "signature": "a3116cf4f1e960223c2cc3088bf387278b6675255209bdeaf96a2f316a2fadc1"
}

Response samples

Content type
text/plain
OK

Retrieve Service List

Authorizations:
bearerAuth

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Retrieve Service Details

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}

Retrieve List of Channels for the Service

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{}

Retrieve Transaction List

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": [
    ],
  • "pagination": {
    }
}

Generate Transaction

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

Request Body schema: application/json
amount
required
number <float> >= 1

Transaction amount

currency
string
Default: "PLN"

Transaction currency

description
string <= 64 characters

Description of the transaction provided by the partner, displayed on the payment gateway

control
string <= 255 characters

Field for use by the partner

object or null

Basic information about the payer

object or null (paymentCustomerFull)
object or null (paymentCustomerFull)
Array of objects or null (paymentCartItem)
object or null
directChannel
string

In this field, you can send the channel ID, and the payer will be redirected directly to the specified channel e.g., when specifying blik, they will be redirected directly to the BLIK payment gateway

channels
Array of strings or null

Array of payment channel IDs that will be displayed to the payer at the gateway after being redirected to the transaction URL
The list of available channels and their IDs can be obtained here Retrieve list of channels for the service

object or null

Object in which we can define which types of channels should be available at the payment gateway

referer
string [ 6 .. 64 ] characters

Responses

Request samples

Content type
application/json
{
  • "amount": 1,
  • "currency": "PLN",
  • "description": "string",
  • "control": "string",
  • "customer": {},
  • "billing": {
    },
  • "shipping": {
    },
  • "cart": [
    ],
  • "returns": {
    },
  • "directChannel": "string",
  • "channels": [
    ],
  • "channelTypes": {
    },
  • "referer": "string"
}

Response samples

Content type
application/json
{}

Retrieve Transaction Details

Authorizations:
bearerAuth
path Parameters
serviceId
required
string (ServiceId) = 8 characters ^[0-9a-f]{8}$

Service ID

transactionId
required
string <uuid> (TransactionId) = 36 characters ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]...

Id transakcji

Responses

Response samples

Content type
application/json
{
  • "success": true,
  • "data": {
    }
}