/refund_debit_card

This endpoint initiates a refund to an end user's successfully linked debit card.

📘

NOTE

The available balance in the end user's Sila wallet must be equal or greater than the refund amount for a successful refund.

Requests

The transaction_id key is required and is used to uniquely identify the transaction to refund.

Authorization / Authentication

Apps using Access Token Authorization

Use a valid access token in an Authorization: Bearer request header.

See Authenticating with an Access Token for more details.

Apps using ECDSA Authentication

Both authsignature and usersignature headers are required for this request. The usersignature header should be generated with a keypair registered to the user (either registered from the /register endpoint or the /register_wallet endpoint).

See the section on ECDSA Authentication for more detail about ECDSA signature generation.

Note - We recently renamed the field auth_handle to app_handle. For backward compatibility, auth_handle is still valid but has been removed from our documentation.

You cannot request a refund on a transaction if the associated debit card has been unlinked/deleted.

POST /0.2/refund_debit_card HTTP/1.1
sandbox.silamoney.com
Content-Type: application/json
// if using OAuth2
Authorization: Bearer [GENERATED JWT TOKEN HERE]
// if using ECDSA
authsignature: [GENERATED AUTHSIGNATURE HEX STRING HERE]
usersignature: [GENERATED USERSIGNATURE HEX STRING HERE]

{
  "header": {
    "created": 1234567890, 
    "auth_handle": "handle.silamoney.eth", 
    "user_handle":"user.silamoney.eth", 
    "reference": "<your unique id>"
  },
  "transaction_id": "<transaction_id>"
}

***

HTTP/1.1 200 OK

{
  "success": true,
  "reference": "6f8a23c0-4122-401c-b8c2-38847a8dd051",
  "message": "A refund request is in progress for debit card transaction 881ac1ba-400c-44ed-b4bd-d82f34cea273.",
  "status": "SUCCESS",
  "response_time_ms": "883"
}

Responses