Skip to main content

API integration

Refunds can be made both for the full amount of a split payment and for all or part of the amount of a separate subpayment included in it.

Interaction format:

An image from the static

Refund of the full amount of the split payment (full refund)

Peculiarities of using this integration to refund the full payment amount:

  1. A request to the Financial Line API for a refund can only be applied to (purchase) or (capture) transactions with the successful (success) statuses.
  2. Use the HTTP POST method.

Request parameters:

ParameterTypeRequiredDescription
pos_idUUIDMerchant's identifier (POS_ID)
order_idStringMerchant's order identifier to be captured (max length is 32 characters)
order_currencyCURRENCYCurrency of original order
commentStringRefund comment. Can be used for describing reasons of refund or for passing another data about operation (max length is 2048 characters)
server_urlURLWebhook notification will be sent to this URL
splitArray[SplitPayment]Split payment properties

Request example:

$ curl "https://api.finline.io/api/v1/split/refund" \
-H "Content-Type: application/json" \
-H "X-API-AUTH: CPAY {API_KEY}:{API_SECRET}" \
-H "X-API-KEY: {ENDPOINTS_KEY}" \
-X POST -d '{
"pos_id": "{POS_ID}",
"order_id": "123",
"order_currency": "UAH",
"comment": "10101",
"server_url": "https://callback.blackhole.com/callback/capture",
"split":[
{
"amount": 70,
"sub_merchant_id": "{SUB_MERCHANT_ID_1}"
},
{
"amount": 30,
"sub_merchant_id": "{SUB_MERCHANT_ID_2}"
}
]
}'

Response parameters:

ParameterTypeDescription
operation_idUUIDUnique Financial Line refund identifier
payment_idUUIDFinancial Line payment identifier of primary operation
order_idStringMerchant's order_id of primary operation (max length is 32 characters)
transaction_idUUIDUnique Financial Line transaction identifier
pos_idUUIDMerchant's identifier (POS_ID)
modeMODEdirect
methodMETHODrefund
amountNumberActual refund amount
currencyCURRENCYTransaction currency
statusSTATUSTransaction status
status_codeSTATUS_CODEFinancial Line payment status code
status_descriptionSTATUS_DESCRIPTIONFinancial Line payment status code description
created_atTIMESTAMPTimestamp when transaction was created
processing_timeTIMESTAMPTimestamp when transaction was updated last time
feeObjectAmount and currency of commission
commentStringRefund comment
split_feeObjectAmount and currency of commission by marketplace and sub-merchants

Response example:

{
"operation_id": "f7d0c7cb-af32-441f-b2af-4d90d4da70e1",
"payment_id": "fdf1a710-8a34-414c-b023-b7e78104301a",
"order_id": "123",
"transaction_id": "4f98dc46-ffff-4ba7-a267-286fe7669894",
"pos_id": "dc728de1-51ef-4ef1-80f7-3b44b07b5667",
"mode": "direct",
"method": "refund",
"amount": 100,
"currency": "UAH",
"status": "success",
"status_code": "1004",
"status_description": "Refund successful.",
"created_at": "2018-10-10T10:10:10.100",
"processing_time": "2018-10-10T10:10:12.000",
"fee": null,
"comment": "10101"
}

Refund of subpayment

If necessary, the full amount of the sub-payment or a separate part of it can be refunded. To carry out such an operation, the request must contain the following additional parameters:

ParameterTypeRequiredDescription
amountNumberTransaction amount
sub_merchant_idUUIDUnique Sub merchant identifier (to get the identifier, please contact support at mailto:support@finline.io)
caution

When refunding several sub-payments, separate requests must be made indicating the corresponding sub-merchants.

Next steps

To test the refund payment process:

  • Carry out a split purchase transaction or a ‘pre-authorization - capture’ split payment combination using the authentication data of the test project.
  • Initiate a secondary operation of refund for the above transaction.
  • Configure webhooks.
  • Use the test data to obtain different operation result codes.
  • Handle received errors.

Going live

Upon activation of the live project by our Compliance Team, use its authentication data instead of the one of the test project.

See also: