Card

（payProduct=18）

Payment Process

1. The user places an order on the merchant's website/app and selects Card payment;

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

3. Supefina returns the card payment URL address;

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 https://api.supefina.tech/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	Country number Reference: Dictionary table - country number Peru: PER
currency	String	Yes	Currency Reference: Dictionary Table - Currency Peruvian Sol: PEN
orderAmount	String	Yes	The amount of the order The unit peso, which needs to be divided into decimal places, supports two decimal places
merId	String	Yes	Merchant ID Merchant ID acquisition path: Supefina Merchant Background - Merchant Management - Basic Information - Merchant IDID
merOrderNo	String	Yes	Merchant order number
nonceStr	String	Yes	Random strings The length cannot exceed 32 bits
payProduct	String	Yes	Payment type Card：18
checkOut	Boolean	Yes	Cash register true: The cashier is required false: The cash register is not required Pass true
returnUrl	Boolean	No	Return address where the payment is complete
callbackUrl	String	No	Callback address For details, see Notification Callbacks
productName	String	Yes	The title of the product The maximum number of characters is 50
productQuantity	Integer	No	The number of units Radius[0,1000]
customerEmail	String	No	Customer's email address 3-256 characters The e-commerce industry must be transmitted
receiverAddressMain	String	No	Address, street 0-50 characters The e-commerce industry must be transmitted
receiverAddressExtra	String	No	Address, community, house number 0-50 characters The e-commerce industry must be transmitted
receiverCity	String	No	Recipient city 0-50 characters, can include spaces, hyphens, apostrophes, commas, and dots The e-commerce industry must be transmitted
receiverProvince	String	No	The recipient's province 0-40 characters Parameter：https://en.wikipedia.org/wiki/ISO_3166-2 Example: NY The e-commerce industry must be transmitted
receiverCountry	String	No	Recipient country Reference: Dictionary Table - Country Number Example: BRA The e-commerce industry must be transmitted
receiverZipCode	String	No	Zip code 0-12 letters or numbers The e-commerce industry must be transmitted
receiverPhone	String	No	Recipient's phone 5-20 characters, add area code. For example: [phone] The e-commerce industry must be transmitted
alias	String	No	Username 0-60 characters A must-have for the gaming industry
sign	String	Yes	signature For details, please refer to: Signature algorithm
customerName	String	Yes	Username
lastName	String	No	The user's last name
customerIdentification	String	No	Proof of identity (e.g. ID number)
customerIdentificationType	String	No	Type of identification (e.g. ID card) Type of identification
description	String	Yes	description It cannot contain special symbols and should not exceed 200 characters in length

Sample request

{
  "countryId": "PER",
  "currency": "PEN",
  "payProduct": "18",
  "productName": "test pruduct name",
  "productQuantity": 1,
  "orderAmount": "200",
  "merId": "0001635350534710",
  "merOrderNo": "20240509087436S20P0154104514",
  "nonceStr": "555016487033129560298749615154",
  "checkOut": "true",
  "returnUrl": "http://www.bing.com",
  "callbackUrl": "http://8.130.9.219:8899/api/supefina/transactions/test/zx",
  "receiverAddressMain":"Sample street 357",
  "receiverAddressExtra":"Apt 2",
  "receiverCity":"Receiver City",
  "receiverCountry":"PER",
  "receiverPhone":"[phone]",
  "receiverProvince":"Example statex",
  "receiverZipCode":"01245",
  "description": "test pruduct desc",
  "customerIdentification": "23443333",
  "customerIdentificationType": "00",
  "customerName": "cName",
  "lastName": "lName",
  "customerPhone": "[phone]",
  "customerEmail": "[email protected]",
  "sign": "R9d1Enp0XUS5YMwv0EP$blm9mWTWwyoB"  
}

Response parameters

Variable name	type	description
code	String	Response coding For details, see Response Status Code
data	Object	Response data
amount	BigDecimal	The amount of the order
currency	String	Currency Reference: Dictionary Table - Currency Peruvian Sol: PEN
merCode	String	Merchant ID
merOrderNo	String	Merchant order number
url	String	Transaction links
msg	String	Response Information

Sample response

{
    "code": "200",
    "msg": "success ",
    "data": {
        "merCode": "0001635350534710",
        "merOrderNo": "20240509087436S20P0154104514",
        "amount": 200,
        "url": "https://h5.supefina.tech/kushki?token=ee808f7c1af54c4aae99d8579a3444d7",
        "currency": "PEN"
    }
}

Callback notifications

Submission method：POST

Variable name	type	description
amount	String	The amount of the order
countryId	String	Country number Reference: Dictionary table - country number Peru: PER
fee	String	Advance handling fee will be charged
identifier	String	Payment Reference Clabe
merId	String	Merchant ID
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	Transaction status For details, please refer to: Dictionary Table - Trading Order Status
supefinaOrderId	String	Supefina order number
transactionType	String	The type of transaction 01: Payin 02: Payout

An example of a callback notification

{
    "amount": "200.00",
    "countryId": "PER",
    "fee": "11.48",
    "identifier": "078018503",
    "merId": "8302858375850055",
    "merOrderId": "20240509087436S20P0154104514",
    "nonceStr": "f861c17d-64eb-494a-be67-79066b",
    "realityAmount": "200.00",
    "realityFee": "11.48",
    "reference": "0117ed5c-3bce-4d5c-8740-a346ce76e8b4",
    "sign": "8AC0AEB3BF6CC99632C8D7FDF4CED101",
    "status": "01",
    "supefinaOrderId": "202405090301003498176b135384e",
    "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";
}

Test data

The test environment provides full payment functionality, but it is only simulated processing with no actual banking transactions.

Below you will find some test cards that you can use in Test Mode (UAT) to ensure that your integration is ready. Use them with any CVV, enter a future expiration date.

If the order amount in the test environment is higher than 1000, the 3DS authentication mode will be triggered, once the 3DS mode appears, enter 1234 as the verification code.

• Test card number for 3D Secure Verified transactions:

  • 4456528080389860

  • 4456529267234200

  • 4456529165328302

  • 4456524869770255

  • 4456523340069956

• Test card number for transactions rejected by 3D Secure Authentication:

  • 5451951574925480

• Test card number for transactions rejected without 3D Secure authentication:

  • 4349008516656431

If you encounter an abnormal status code during the test, please contact Supefina operation personnel directly.