We work hard to ensure everyone who uses ZWITCH gets the best experience. Every day we take small steps towards developing new products, enhancing existing features, and improving the performance of our system. We also fix (the occasional) bug in the system.

Below is a list of new feature releases, product improvements, and bug fixes from February 2022.

📘

Note

• Except for breaking changes, all other changes are backward compatible.
• Currently, we work on a daily release cycle. We push changes to the production environment as they are developed. However, we will notify you about breaking changes, new feature releases, and major enhancements via email before they are released.

🎉 Enhancements

Below are the enhancements we made in February 2022.

Beneficiaries

We have made the following changes to the Beneficiary APIs.

Beneficiary Name - Special Character Support

The name parameter in Beneficiary APIs now supports a few special characters. The following characters are now supported by the name parameter.

• a-z
• A-Z
• 0-9
• Space
• Apostrophe (’)
• Hyphen (-)
• Underscore (_)
• Forward Slash (/)
• Round brackets
• Period (.)

Deleted At Timestamp

We have added a deleted_at timestamp to the Delete Beneficiary API response.

Below is an example of the new Delete Beneficiary API response.

{
  "id": "vab_HETIZ3DEYP2XxWnU1V9Qk2NI0",
  "object": "beneficiary",
  "deleted": true,
  "account_id": "va_tQJApUz8KATaaJmbbV9NqurNs",
  "deleted_at": 1646811350
}

Webhooks

We have made a few developer experience enhancements to the Webhook module.

Verify PAN Webhook Event

PAN verification is mandatory to activate a savings account. We automatically initiate PAN verification during the account creation process. Alternatively, you might want to manually verify your customer’s PAN details using our Verify PAN APIs.

In both cases, it is important for you to know the PAN verification status. This allows you to keep your customers informed and perform further actions as per your business needs.

We have added the following webhook events to keep you informed about the Aadhaar verification status.

• kycs.pan.created: Triggered when the Verify PAN API call is successfully made automatically by ZWITCH or manually by you.

Below is a sample payload for the webhook event.

{
  "id": "evl_SnAVQuMNc85fJBOXJjlcNhsl5",
  "object": "event",
  "name": "kycs.pan.created",
  "is_sandbox": true,
  "data": {
    "object": {
      "id": "pan_1IEU3w1DDAqczfsDUyMA4tQi1",
      "object": "pan_verification",
      "pan": "ADBPH4883P",
      "name_on_pan": "NAME AS PER PAN RECORDS",
      "status": "success",
      "merchant_reference_id": "1000027",
      "metadata": {
        "key_1": "DD",
        "key_2": "XOF"
      },
      "created_at": 1646919610,
      "is_sandbox": true
    }
  }
}

Bank Account Verification Webhook Event

We have added the following webhook event to keep you informed about the bank account verification transactions.

• verifications.bank_account.created: Triggered when the Verify Bank Account API call is successfully made.

Below is a sample payload for the webhook event.

{
  "id": "evl_RlDKAYhtxrXM5lHa1g0qZ6gwR",
  "object": "event",
  "name": "verifications.bank_account.created",
  "is_sandbox": true,
  "data": {
    "object": {
      "id": "accver_IRutjgMyHkyUFFNXaOp6752iz",
      "object": "bank_account_verification",
      "bank_account_number": "10000000000026",
      "bank_ifsc_code": "HDFC0000123",
      "name_as_per_bank": "Name as per bank",
      "force_penny_drop": false,
      "force_penny_drop_amount": 1.23,
      "status": "success",
      "message": "Transaction Successful",
      "last_verified_at": "2022-03-10",
      "metadata": {
        "key_1": "DD",
        "key_2": "XOF"
      },
      "merchant_reference_id": "1000026",
      "created_at": 1646919498,
      "is_sandbox": true
    }
  }
}

🛠️ Bug Fixes

Below is a list of bugs we fixed in February 2022.

General

Values against the currency parameter in the source_details object in the Get Account Statement API are now returned in lower case. Earlier, values were returned upper case.

Webhooks

Metadata Format in Webhooks

We have fixed how metadata is formatted in webhooks.

Below is an example of how metadata was returned earlier.

{
  "metadata": "{\"key_1\":\"DD\",\"key_2\":\"XOF\"}"
}

Below is an example of how we now return metadata in webhooks.

"metadata": {
  "key_1": "DD",
  "key_2": "XOF"
}

Errors

401 errors are now wrapped within the error object.

Below is an example of how we used to send 401 errors.

{
  "type": "authentication_error",
  "message": "Invalid secret key."
}

Below is an example of how we send 401 errors now.

{
  "error": {
    "type": "authentication_error",
    "message": "Invalid secret key."
  }
}