Introduction

API Reference Guide

API Changelog

Understand Razorpay APIs

Authentication

Sandbox Setup

Best Practices

Glossary

Payments

Orders

Payments

Downtime

Settlements

Instant Settlements

Refunds

Disputes

Documents

Customers

Payment Links

QR Codes

Invoices

Subscriptions

Route

Smart Collect

Smart Collect Entity

Create a Customer Identifier With Bank Account Receiver

Close a Customer Identifier

Fetch a Customer Identifier Using ID

Fetch all Customer Identifiers

Fetch Payments for a Customer Identifier

Fetch Payments Made By Bank Transfer

Fetch Payments Using UTR Number

Update a Customer Identifier

Smart Collect TPV

Smart Collect With TPV Entity

Create a Customer Identifier With TPV

Add an Allowed Payer With TPV

Fetch a Customer Identifier Using ID With TPV

Fetch All Customer Identifiers With TPV

Fetch Payments for a Customer Identifier With TPV

Fetch Payment Details Using ID and Transfer Method With TPV

Delete an Allowed Payer With TPV

Smart Collect 2.0

Smart Collect 2.0 Entity

Create Customer Identifier With VPA and Bank Account Receivers (Smart Collect 2.0)

Add VPA Receiver to an Existing Customer Identifier (Smart Collect 2.0)

Fetch Payments Made Using UPI (Smart Collect 2.0)

TPAP Pro

Customer Onboarding

Accounts Management

Payments

Mandates

Complaints

UPI Number

UPI Lite

Bills

About Bills

Bills Entity

Create a Bill

Update a Bill

Delete a Bill

Partners

Account

Product Configuration

Stakeholder

Documents

Webhooks

Payout APIs

Get Started

Account Validation

Fetch Balance

Composite Account Validation

Contacts

Fund Accounts

Payouts

Payouts to Cards

Payout Composite

Payouts Approval

Payout Idempotency

Payout Links

Payout Wallet - Amazon

Transactions

Api

Payments

Smart Collect Tpv

Entity

API Test Keys

Smart Collect With TPV Entity

The Smart Collect with TPV entity has the following parameters:

Is this page helpful?

Entity

1
{
2
  "id":"va_CaVE4QbyJvQRdk",
3
  "name":"Acme Corp",
4
  "entity":"virtual_account",
5
  "status":"active",
6
  "description":"Customer Identifier created for Gaurav Kumar",
7
  "notes":{
8
    "flat no":"105"
9
  },
10
  "amount_paid":0,
11
  "customer_id":"cust_805c8oBQdBGPwS",
12
  "receivers":[
13
    {
14
      "id": "ba_DzXNNxY8yQu5iV",
15
      "entity": "bank_account",
16
      "ifsc":"RATN0VAAPIS",
17
      "bank_name": "RBL Bank",
18
      "name": "Acme Corp",
19
      "notes": [],
20
      "account_number": "2223333230231378"
21
    }
22
  ],
23
  "allowed_payers": [
24
    {
25
      "type": "bank_account",
26
      "id":"ba_DlGmm9mSj8fjRM",
27
      "bank_account": {
28
        "ifsc": "UTIB0000013",
29
        "account_number": "914010012345679"
30
      }
31
    },
32
    {
33
      "type": "bank_account",
34
      "id":"ba_Cmtnm5tSj6agUW",
35
      "bank_account": {
36
        "ifsc": "UTIB0000014",
37
        "account_number": "914010012345680"
38
      }
39
    }
40
  ],
41
  "close_by": 1581615838,
42
  "closed_at": null,
43
  "created_at": 1577962694
44
}
id
string

The unique identifier of the Customer Identifier.

name
string

The merchant billing label as it appears on the Dashboard.

entity
string

Indicates the type of entity. Here, it is virtual account.

status
string

Indicates whether the Customer Identifier is in active or closed state.

description
string

A brief description about the Customer Identifier.

amount_expected
integer

The amount expected by the merchant.

amount_paid
integer

The amount paid by the customer into the Customer Identifier.

notes
json object

Any custom notes you might want to add to the Customer Identifier can be entered here. Check the

Notes section

to know more.

customer_id
string

Unique identifier of the customer the Customer Identifier is linked with. Check the

Customer API

section to know more.

receivers
json object

Configuration of desired receivers for the Customer Identifier.

Show child parameters (7)

allowed_payers
array

Details of customer bank accounts which will be allowed to make payments to your Customer Identifier. The parent parameter under which the customer bank account details must be passed as child parameters. You can add account details of 10 allowed payers for a Customer Identifier. For more details, refer to the

Third Party Validation

section.

Show child parameters (3)

close_by
integer

UNIX timestamp at which the Customer Identifier is scheduled to be automatically closed. The time must be at least 15 minutes after current time. The date range can be set till 2147483647 in UNIX timestamp format (equivalent to Tuesday, January 19, 2038 8:44:07 AM GMT+05:30). Any request beyond 2147483647 UNIX timestamp will fail.

closed_at
integer

UNIX timestamp at which the Customer Identifier is automatically closed.

created_at
integer

UNIX timestamp at which the Customer Identifier was created.

Smart Collect With TPV Entity

The Smart Collect with TPV entity has the following parameters:

Is this page helpful?

id
string

The unique identifier of the Customer Identifier.

name
string

The merchant billing label as it appears on the Dashboard.

entity
string

Indicates the type of entity. Here, it is virtual account.

status
string

Indicates whether the Customer Identifier is in active or closed state.

description
string

A brief description about the Customer Identifier.

amount_expected
integer

The amount expected by the merchant.

amount_paid
integer

The amount paid by the customer into the Customer Identifier.

notes
json object

Any custom notes you might want to add to the Customer Identifier can be entered here. Check the

Notes section

to know more.

customer_id
string

Unique identifier of the customer the Customer Identifier is linked with. Check the

Customer API

section to know more.

receivers
json object

Configuration of desired receivers for the Customer Identifier.

Show child parameters (7)

allowed_payers
array

Details of customer bank accounts which will be allowed to make payments to your Customer Identifier. The parent parameter under which the customer bank account details must be passed as child parameters. You can add account details of 10 allowed payers for a Customer Identifier. For more details, refer to the

Third Party Validation

section.

Show child parameters (3)

close_by
integer

UNIX timestamp at which the Customer Identifier is scheduled to be automatically closed. The time must be at least 15 minutes after current time. The date range can be set till 2147483647 in UNIX timestamp format (equivalent to Tuesday, January 19, 2038 8:44:07 AM GMT+05:30). Any request beyond 2147483647 UNIX timestamp will fail.

closed_at
integer

UNIX timestamp at which the Customer Identifier is automatically closed.

created_at
integer

UNIX timestamp at which the Customer Identifier was created.

Entity

1
{
2
  "id":"va_CaVE4QbyJvQRdk",
3
  "name":"Acme Corp",
4
  "entity":"virtual_account",
5
  "status":"active",
6
  "description":"Customer Identifier created for Gaurav Kumar",
7
  "notes":{
8
    "flat no":"105"
9
  },
10
  "amount_paid":0,
11
  "customer_id":"cust_805c8oBQdBGPwS",
12
  "receivers":[
13
    {
14
      "id": "ba_DzXNNxY8yQu5iV",
15
      "entity": "bank_account",
16
      "ifsc":"RATN0VAAPIS",
17
      "bank_name": "RBL Bank",
18
      "name": "Acme Corp",
19
      "notes": [],
20
      "account_number": "2223333230231378"
21
    }
22
  ],
23
  "allowed_payers": [
24
    {
25
      "type": "bank_account",
26
      "id":"ba_DlGmm9mSj8fjRM",
27
      "bank_account": {
28
        "ifsc": "UTIB0000013",
29
        "account_number": "914010012345679"
30
      }
31
    },
32
    {
33
      "type": "bank_account",
34
      "id":"ba_Cmtnm5tSj6agUW",
35
      "bank_account": {
36
        "ifsc": "UTIB0000014",
37
        "account_number": "914010012345680"
38
      }
39
    }
40
  ],
41
  "close_by": 1581615838,
42
  "closed_at": null,
43
  "created_at": 1577962694
44
}