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

Transfer

(payProduct=12)

AnteriorPeruSiguienteCash

Última actualización hace 18 días

Payment Process

1. The user places an order on the merchant's website/app and selects Transfer to pay.

2. The merchant initiates a Transfer payment request to Supefina;

3. Supefina returns the URL address of Transfer 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

callbackUrl

String

No

Callback address

checkOut

Boolean

No

Cash register

true: The cashier is required

false: The cash register is not required

It is recommended to pass true

countryId

String

Yes

Country number

Peru: PER

currency

String

Yes

Currency

Peruvian Sol: PEN

customerEmail

String

Yes

The user's email address

customerIdentification

String

Yes

The ID number of the user

00: ID card (CC), 8 digits

01: Alien Identity Card (CE), more than 9 digits

02: Tax identification number, 11 digits

03: Passport, more than 9 digits

04: Departure Document (PAR)

05: Military Identification (LMI)

The same certificate number customerIdentification can be collected no more than 20 times per day

customerIdentificationType

String

Yes

The type of user ID

00: Identification Card (CC)

01: Alien Identity Card (CE)

02: Tax identification number

03: Passport (PAS)

04: Departure Document (PAR)

05: Military Identification (LMI)

customerName

String

Yes

User's name

customerPhone

String

Yes

Subscriber's phone, 9 digits

Example: 975728895

expireTimeL

Long

No

Expiration time Unit: seconds; Default value: 1 day; Maximum: 30 days; Minimum: None

lastName

String

Yes

The user's last name

merId

String

Yes

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

merOrderNo

String

Yes

Merchant order number

nonceStr

String

Yes

Random strings The length cannot exceed 32 bits

orderAmount

String

Yes

订The amount of the order

payProduct

String

Yes

Transfer:12

sign

String

Yes

signature

Sample request

{
    "callbackUrl": "https://test.com",
    "checkOut": true,
    "countryId": "PER",
    "currency": "PEN",
    "customerEmail": "[email protected]",
    "customerIdentificationType": "00",
    "customerName": "Test Name",
    "customerPhone": "975728895",
    "lastName": "Name",
    "merId": "8302769856320671",
    "merOrderNo": "128128855539891808",
    "nonceStr": "deposit",
    "orderAmount": "60.00",
    "payProduct": "12",
    "sign": "7F4F3F7CF9EDBC08A9F91B8739409135"
}

Response parameters

Variable name
type
description

code

String

Response coding

data

Object

Response data

amount

BigDecimal

The amount of the order

fee

BigDecimal

Advance handling fee will be charged

identifier

String

Payment Reference

merCode

String

Merchant ID

merOrderNo

String

Merchant order number

supefinaOrderNo

String

sSupefina order number

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

msg

String

Response Information

Sample response

{
    "code": "200",
    "data": {
        "amount": 60.00,
        "fee": 3.80,
        "identifier": "90984378332",
        "merCode": "8302769856320671",
        "merOrderNo": "128128855539891808",
        "supefinaOrderNo": "20240520010101902996cca341c4a",
        "transactionStatus": "00",
        "url": "https://secure.payv.co/ahsas"
    },
    "msg": "success "
}

Callback notifications

Submission method:POST

Variable name
type
description

amount

String

The amount of the order

countryId

String

Country number

fee

String

Advance handling fee will be charged

identifier

String

Payment Reference

merId

String

Merchant code

merOrderId

String

Merchant order number

nonceStr

String

Random strings The length cannot exceed 32 bits

realityAmount

String

Paid-in amount

realityFee

String

Actual handling fee

reference

String

identifier

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": "60.00",
    "countryId": "PER",
    "customerName": "Test Name",
    "fee": "3.80",
    "identifier": "90984378332",
    "merId": "8302769856320671",
    "merOrderId": "128128855539891808",
    "nonceStr": "65b9c17e-8164-4513-bafa-cefc4d",
    "realityAmount": "60",
    "realityFee": "3.80",
    "reference": "90984378332",
    "sign": "3B003A010EDAA9695ED5F9777F5D77F0",
    "status": "01",
    "successTime": 1716193414000,
    "supefinaOrderId": "20240520010101902996cca341c4a",
    "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";
}

For details, see

Reference:

Reference:

For details, see

For details, please refer to:

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