Supefina Payment API
English
English
  • Welcome to Supefina's API documentation
    • Quick Start
    • Signature algorithms
    • Notification callback description
    • Cashier (only for merchants in the e.commerce industry)
      • 🇲🇽Mexico
      • 🇵🇪Peru
    • Payin
      • 🇲🇽Mexico
        • SPEI
        • Cash
        • Card
        • Payin Simulation (SPEl)
        • Payin Simulation (Cash &Card)
      • 🇨🇴Colombia
        • PSE
        • Bancolombia
        • Cash
        • All-Checkout
        • Payin simulation
      • 🇵🇪Peru
        • Transfer
        • Cash
        • Wallet
        • Card
        • Payin simulation
      • 🇧🇷Brazil
        • PIX
        • Payin simulation
      • 🇪🇨Ecuador
        • Transfer
        • Cash
        • Card
        • Wallet
        • Payin simulation
      • 🇦🇷Argentina
        • Debin
    • Payout
      • 🇲🇽Mexico
        • SPEI
        • Explanation of the reason for the payout failure
        • payout simulation
      • 🇨🇴Colombia
        • Transfer
        • Transfiya
        • Explanation of the reason for the payment failure
        • Payout simulation
      • 🇵🇪Peru
        • Transfer
        • Explanation of the reason for the payout failure
        • Payout simulation
      • 🇨🇱Chile
        • Transfer
        • Payout simulation
      • 🇧🇷Brazil
        • PIX
        • Explanation of the reason for the payment failure
        • Payout simulation
      • 🇪🇨Ecuador
        • Transfer
        • EC Transfer
        • Payout simulation
      • 🇦🇷Argentina
        • Transfer
    • Inquire
      • Transaction inquiries
      • Balance inquiry
      • Credential inquiry
      • Query the settlement status
    • Dictionaries and Resources
      • Response status code
      • Dictionary table
      • Download
      • Test parameters
Con tecnología de GitBook
En esta página
  • Payment Process
  • The address of the request
  • Request parameters
  • Sample request
  • Response parameters
  • Callback notifications
  1. Welcome to Supefina's API documentation
  2. Payin
  3. Colombia

All-Checkout

(payProduct=05)

AnteriorCashSiguientePayin simulation

Última actualización hace 10 días

Payment Process

1. The user places an order on the merchant's website/app and selects All-Checkout to pay;

2. The merchant initiates an All-Checkout payment request to Supefina;

3. Supefina returns the URL address of the All-Checkout payment;

4. The merchant will open the address on the user's side;

5. The user shall verify and pay according to the prompts on the page;

6. The user pays successfully;

7. Supefina will notify the merchant of the payment success information.

The address of the request

The name of the environment
URL

SandBox

POST http://8.130.9.219:8899/api/supefina/transactions/payin

Formal environment

POST https://api.supefina.net/api/supefina/transactions/payin

Request parameters

Request header

Key
Value

Content-Type

application/json

Request body

Variable name
type
Required
description

countryId

String

Yes

currency

String

Yes

orderAmount

String

Yes

The amount of the order 3000 >= orderAmount <= 2000000

Decimals are not supported

payProduct

String

Yes

merId

String

Yes

Merchant ID Merchant ID acquisition path: Supefina Merchant Background - Merchant Management - Basic Information - Merchant ID

merOrderNo

String

Yes

Merchant order number

sign

String

Yes

nonceStr

String

Yes

Random strings The length cannot exceed 32 bits

customerEmail

String

Yes

The user's email address The email username cannot be a number (for example, [email protected]) and the same email address cannot have more than 20 payment requests per day.

customerName

String

Yes

Username

customerPhone

String

Yes

User phone Ten digits starting with 3 are required

customerIdentification

String

Yes

The ID number of the user

checkOut

Boolean

Yes

Cash register

true: The cashier is required

false: The cash register is not required It is recommended to pass true

customerAccount

String

No

User Accounts checkOut must be passed when it is false

lastName

String

No

The user's last name checkOut must be passed when it is false

customerIdentificationType

String

No

The type of user ID 00:Identification Card(CC) 01:Alien Identity Card(CE) 02:Tax identification number

03: Passport

06: Miscellaneous

07: Proof of citizenship

08: Residence permit

checkOutmust be passed when it is false

customerAddress

String

No

User's address checkOut must be passed when it is false

tipo_persona

String

No

Payment Subject checkOut must be passed when it is false

bankId

String

No

Bank code See also:

https://api.supefina.net/api/supefina/transactions/internal/getEbixuBankList checkOut must be passed when it is false

expireTimeL

Long

No

Expiration time Unit: seconds; Default: 10 minutes, maximum: 10 minutes

callbackUrl

String

No

Callback address

description

String

Yes

description

It cannot contain special symbols and should not exceed 200 characters in length

Sample request

{
    "callbackUrl": "http://8.130.9.219:8899/api/supefina/transactions/test/zx",
    "checkOut": true,
    "countryId": "COL",
    "currency": "COP",
    "customerEmail": "[email protected]",
    "customerIdentification": "123456",
    "customerName": "test",
    "customerPhone": "1234567890",
    "merId": "8202325858590233",
    "merOrderNo": "toppay001",
    "nonceStr": "123",
    "orderAmount": "3001",
    "payProduct": "05",
    "sign": "0F569F49F68884C3E490E44BB8FCF68E",
    "description":"Supefina"
}

Response parameters

Variable name
type
description

code

String

msg

String

Response Information

data

Object

Response data

merCode

String

Merchant ID

merOrderNo

String

Merchant order number

supefinaOrderId

String

Supefina order number

amount

BigDecimal

The amount of the order

fee

String

Advance handling fee will be charged

identifier

String

Payment Reference

transactionStatus

String

Order status Whether the initiation status of the order is successful or not has nothing to do with the real transaction status of the order. 00:The order is successful 04:Failed to place an order

url

String

Transaction links

Sample response

{
    "code": "string",
    "msg": "string",
    "data": {
        "merCode": "string",
        "merOrderNo": "string",
        "supefinaOrderNo": "string",
        "amount": 0,
        "fee": 0,
        "transactionStatus": "string",
        "url": "string",
        "identifier": "string"
    }
}

Callback notifications

Submission method:POST

Variable name
type
description

amount

String

The amount of the order

countryId

String

Country number

customerName

String

Username

fee

String

Advance handling fee will be charged

merId

String

Merchant ID

merOrderId

String

Merchant order number

msg

String

message

nonceStr

String

Random strings The length cannot exceed 32 bits

realityAmount

String

Paid-in amount

realityFee

String

Actual handling fee

sign

String

signature

status

String

successTime

Date

The time at which the transaction was successful UTC time

supefinaOrderId

String

Supefina order number

transactionType

String

The type of transaction 01:Payin 02:Payout

An example of a callback notification

{
    "amount": "20000.00",
    "countryId": "COL",
    "customerName": "Grace Shaw",
    "fee": "1000.00",
    "merId": "8301409897370054",
    "merOrderId": "R20240619052050314",
    "msg": "",
    "nonceStr": "8b0c8dcd-14b6-4fef-a970-c914dc",
    "realityAmount": "20000",
    "realityFee": "1000.00",
    "sign": "FD1DD91503C4EC282E8CA01591973921",
    "status": "01",
    "successTime": 1718775146000,
    "supefinaOrderId": "2024061900010012b16f19beca043",
    "transactionType": "01"
}

Callback notification response

After the merchant successfully receives the callback, it needs to return the specified string synchronously: SUCCESS does not return or returns other content by default, and the notification fails As:

public String test(){
	return "SUCCESS";
}

Country number Reference: Columbia,COL

Currency Reference: Colombian Peso:COP

All-Checkout:05

signature

For details, see

Response coding For details, see

For details, please refer to:

🇨🇴
Dictionary table - country number
Dictionary Table - Currency
Payment type
For details, please refer to: Signature algorithm
Notification Callbacks
Response Status Code
Transaction status
Dictionary Table - Trading Order Status