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
  • The address of the request
  • How the request is made
  • Response parameters
  • Callback notifications
  • List of Payout banks in Peru
  1. Welcome to Supefina's API documentation
  2. Payout
  3. Peru

Transfer

(payProduct=20)

The address of the request

The name of the environment
URL

SandBox

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

Formal environment

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

How the request is made

Request header

Key
Value

Content-Type

application/json

Request body

Variable name
type
Required
description

account

String

Yes

Beneficiary account number

1. The four major bank account types and digits in Peru:

03--BBVA, current account and savings account with 18 or 20 digits;

04--SCOTIABANK, 10 digits for current accounts and savings accounts;

02--INTERBANK, 13 digits of current accounts and savings accounts;

01--BCP, 00 (current account) has 13 digits and 0 in the 11th digit; 01 (Savings Account) has 14 digits and 0 digits in 12 digits.

2. No special symbols such as decimal points and "-", only pure numbers.

3. Example: 1110333711

accountType

Strin

Yes

Beneficiary account type

00: CORRIENTE (Current Account)

01: AHORROS (Savings Account)

Example: 00

app

String

Yes

The name of the order app

bankName

String

Yes

The name of the bank

callbackUrl

String

No

Callback address

cciNumber

String

No

Beneficiary intermediary account

1. When the bankName is not one of the four major banks (BCP, Interbank, BBVA, Scotiabank), this field must be transmitted.

2. The number of cciNumber digits is 20 digits.

3. No special symbols such as decimal points and "-", only pure numbers.

4. Example: 00911120111033371164

countryId

String

Yes

Country number

Reference: Dictionary table - country number

Peru, PER

currency

String

Yes

Currency

Reference: Dictionary Table - Currency

Peruvian Peso: PEN

customerEmail

String

Yes

Beneficiary's email address

customerIdentification

String

Yes

The ID number of the user

00: Identification Card (DNI), 8 digits

01: Alien Identity Card (CE), ≥ 9 digits

02: Tax Identification Number (RUC), 11 digits

03: Passport (PAS), ≥ 9 digits

Note: Special symbols such as decimal points and "-" are not allowed, only pure numbers.

Example: 42340816

customerIdentificationType

String

Yes

The type of user ID

00: Identification Card (DNI)

01: Alien Identity Card (CE)

02: Tax Identification Number (RUC)

03: Passport (PAS)

Example: 00

customerName

String

Yes

Beneficiary's name

customerPhone

String

Yes

Beneficiary's phone number Area code (+51, 51) + 9-digit mobile phone number, the area code can be passed or not Example:

+51123456789(including area code+51) 51123456789(including area code 51) 123456789(phone number without area code)

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

Pass in 100, which is 100 PEN and supports 2 decimal places

payProduct

String

Yes

Transfer:20

sign

String

Yes

Sample request

{
    "account": "19299172588073",
    "accountType": "01",
    "app": "supefina",
    "bankName": "01",
    "callbackUrl": "https://test.com",
    "countryId": "PER",
    "currency": "PEN",
    "customerEmail": "[email protected]",
    "customerIdentification": "73313761",
    "customerIdentificationType": "00",
    "customerName": "Test Name",
    "customerPhone": "52173996789",
    "merId": "8202157333970291",
    "merOrderNo": "8485233309941743872",
    "nonceStr": "52b6350acc364578b3d25f30a8ee95f3",
    "orderAmount": "105.00",
    "payProduct": "20",
    "sign": "5E57AE7AF2548AA9020C52752C6A963C"
}

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

merCode

String

Merchant ID

merOrderNo

String

Merchant order number

supefinaOrderNo

String

Supefina 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

msg

String

Response Information

Sample response

{
    "code": "200",
    "data": {
        "amount": 105.00,
        "fee": 3.00,
        "merCode": "8202157333970291",
        "merOrderNo": "8485233309941743872",
        "supefinaOrderNo": "2024052001860105b0fae306a6e43",
        "transactionStatus": "00"
    },
    "msg": "success "
}

Callback notifications

Submission method:POST

There are two callback notification statuses for payout. After the successful callback event is successfully received, it is still possible to receive the callback event that the payout status changes, and the payout status changes from success to failure, this kind of order will only appear in the Peruvian inter-bank transfer, the execution of the payout bank will check the account information twice, and the channel will be successful after the first pass, and the bank will check the second time, and find that the account may be locked, the account type cannot be transferred, etc., the bank will not pay, and will notify the channel once a week/month.

Variable name
type
description

amount

String

The amount of the order

countryId

String

Country number Reference: Dictionary table - country number Peru, PER

customerName

String

Beneficiary's name

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

String

The time at which the transaction was successful

supefinaOrderId

String

Supefina order number

transactionType

String

The type of transaction 01:Payin 02:Payout

An example of a callback notification

{
    "amount": "105.00",
    "countryId": "PER",
    "customerName": "Test Name",
    "fee": "3.00",
    "merId": "8202157333970291",
    "merOrderId": "8485233309941743872",
    "msg": "success",
    "nonceStr": "76abf1f3-0486-4c1e-ac2a-1d9e17",
    "realityAmount": "105.00",
    "realityFee": "3.00",
    "sign": "11D7CBC5B0C337F904F227628813F5DE",
    "status": "01",
    "successTime": 1716249060000,
    "supefinaOrderId": "2024052001860105b0fae306a6e43",
    "transactionType": "02"
}

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";
}

List of Payout banks in Peru

01

bcp

02

interbank

03

bbva

04

scotiabank

05

Banco de Comercio

06

BanBif (Banco Interamericano de Finanzas)

07

Banco Pichincha

08

Citibank

09

Banco GNB

10

Banco Santander

11

Banco Azteca

12

Banco Cencosud

13

ICBC PERU BANK

14

Banco de la Nación

15

Caja Cusco

16

Caja Huancayo

17

Caja Maynas

18

Caja Metropolitana

19

Caja Municipal Ica

20

Caja Sullana

21

Caja Tacna

22

Caja Trujillo

AnteriorPeruSiguienteExplanation of the reason for the payout failure

Última actualización hace 22 días

Example: 01, for details, please refer to:

For details, see

signature

For details, see

Transaction status For details, please refer to:

🇵🇪
List of Peruvian payment banks
Notification Callbacks
Payment type
For details, please refer to: Signature algorithm
Response Status Code
Dictionary Table - Trading Order Status
态