Skip to main content

Process Refund

POST 
/v2/deposits/:depositId/refunds/:refundId/status
Feature in development

Refunds are created in PREVIEW state. It creates the Refund resource and validates the refund parameters.

To move the payment forward you must request status change using POST /v2/deposits/{depositId}/refunds/{refundId}/status. This will move the refund in PENDING state.

{
   "status": "PENDING"
}

To confirm the refund for execution use POST /v2/deposits/{depositId}/refunds/{refundId}/status:

{
   "status": "PROCESSING"
}

Poll for status or leverage webhooks for track the refund progress.

Request​

Path Parameters

    depositId stringrequired

    Deposit Id.

    refundId stringrequired

    Refund Id.

Header Parameters

    Content-Type stringrequired

    Default value: application/json

    application/json

Body

    status PaymentStatus (string)required

    Possible values: [PROCESSING, PENDING]

Responses​

Accepted

Schema

    amount int64required

    Refund amount in currency minor units. Refund amount can not exceed the refunded payment amount.

    currencyCode Currency (string)required

    Possible values: >= 3 characters and <= 3 characters

    Currency alphabetic code as specified by ISO 4217

    merchantRefNum MerchantReferenceNumber (string)

    Possible values: <= 255 characters

    This is the merchant reference number created by the merchant and submitted as part of the request. It must be unique for each request and allows cross referencing objects from merchant system to embedded wallet objects.

    id stringrequired

    Refund id generated during creation.

    customerId stringrequired

    Customer id.

    accountId stringrequired

    The account funding the refund. Account id deduced from the relevant deposit.

    slipId string

    Slip identifier. Slip contains list of transactions associated with the withdrawal operations.

    fundingTransactionId string

    Deposit funding transaction id.

    refundTransactionId string

    Refund funding transaction id.

    creationTime date-timerequired

    Represents RFC 3339, section 5.6 date-time.

    expirationTime date-time

    Represents RFC 3339, section 5.6 date-time.

    paymentOption PaymentOptionType (string)required

    Possible values: [RAPID_TRANSFER, BANK_TRANSFER, OFFLINE_BANK_TRANSFER, CARD, PAYSAFECASH, PAGO_EFECTIVO]

    Enumeration of supported Payment Option Types

    status Payment Status (string)required

    Possible values: [PREVIEW, PENDING, PROCESSING, COMPLETED, FAILED, CANCELLED, REFUNDED]

    The payment status:

    • PREVIEW - Payment preview.
    • PENDING - Payment transaction is created and further action is required by the customer.
    • PROCESSING - Payment is scheduled for processing by the payment provider.
    • COMPLETED - Payment is completed. Note that some transactions might be completed from Embedded Wallet point of view, but not from customer point of view, since money movement might take some time outside of the Embedded Wallet network.
    • FAILED - Payment has failed. Check STATUS_REASON property for details.
    • CANCELLED - Payment have been cancelled
    • REFUNDED - Valid only for deposits.
    statusReason string

    Possible values: <= 60 characters

    Status reason for FAILED transaction.

    nextStatus Payment Status (string)[]

    Possible values: [PREVIEW, PENDING, PROCESSING, COMPLETED, FAILED, CANCELLED, REFUNDED]

    Provides the next possible status update the client can request, depending on the chosen payment type and option.

Loading...