Skip to main content
POST
/
ren
/
api
/
v1
/
payin
/
edd
/
save
cURL
curl --request POST \
  --url https://sandbox.dollarpe.xyz/ren/api/v1/payin/edd/save \
  --header 'Content-Type: application/json' \
  --header 'X-API-KEY: <api-key>' \
  --header 'X-SIGNATURE: <api-key>' \
  --header 'X-TIMESTAMP: <api-key>' \
  --data '
{
  "customer_id": "2e104290-07c8-49f1-a5ca-0d27f0078f8a",
  "source_of_income": "SALARY",
  "bank_statement_url": [
    "https://storage.example.com/uploads/bank1.pdf",
    "https://storage.example.com/uploads/bank2.pdf"
  ],
  "bank_statement_passwords": [
    "pass1",
    ""
  ],
  "itr_report_url": [
    "https://storage.example.com/uploads/itr1.pdf",
    "https://storage.example.com/uploads/itr2.pdf"
  ],
  "itr_report_passwords": [
    "pass1",
    ""
  ],
  "purpose": "Investment",
  "account_operator": "FAMILY",
  "account_operator_name": "John Doe",
  "p2p_trading_status": false,
  "supporting_purpose_doc_url": [
    "https://storage.example.com/uploads/example1.pdf",
    "https://storage.example.com/uploads/example2.pdf"
  ],
  "relation_with_account_operator": "brother"
}
'
{
  "status": true,
  "message": "Success",
  "data": {
    "id": "550e8400-e29b-41d4-a716-446655440000",
    "status": "PROCESSING"
  }
}
Payin EDD results apply to both payins and payouts. This means that doing Payin EDD is enough to suffice for both payin and payout EDD requirements.

Error Codes and Messages

API Status CodeResponseReason
400Customer is unverifiedCustomer is added but KYC is unverified
400Customer is unverifiedCustomer does not belong to Organization
400Customer is unverifiedCustomer is not KYC verified
400EDD not requiredEDD for the customer is not currently required or applicable
500Internal Server ErrorInternal Server Error

Authorizations

X-API-KEY
string
header
required

API Key for authentication

X-TIMESTAMP
string
header
required

Current timestamp in seconds since epoch

X-SIGNATURE
string
header
required

HMAC SHA256 signature of the request encoded in Base64

Body

application/json
customer_id
string<uuid>
required

The unique identifier of the quotation

Example:

"2e104290-07c8-49f1-a5ca-0d27f0078f8a"

source_of_income
enum<string>
required
Available options:
SALARY,
BUSINESS_INCOME,
OTHERS
Example:

"SALARY"

bank_statement_url
array
required

array of urls for bank statements in case of multiple.

Example:
[
"https://storage.example.com/uploads/bank1.pdf",
"https://storage.example.com/uploads/bank2.pdf"
]
bank_statement_passwords
array
required

Passwords corresponding to the bank statement PDFs. In case of no password, use empty strings

Example:
["pass1", ""]
itr_report_url
array
required

array of urls for itr reports in case of multiple.

Example:
[
"https://storage.example.com/uploads/itr1.pdf",
"https://storage.example.com/uploads/itr2.pdf"
]
itr_report_passwords
array
required

Passwords corresponding to the itr report PDFs. In case of no password, use empty strings

Example:
["pass1", ""]
purpose
enum<string>
required

Purpose of requesting increased limits / transaction volume

Available options:
Investment,
Trading,
Payments,
Lending / Repayments,
Gifting,
Donations / Charity,
Remittance,
Legal Settlements
Example:

"Investment"

account_operator
enum<string>
required
Available options:
SELF,
FAMILY,
THIRD PARTY
Example:

"FAMILY"

account_operator_name
string
required
Example:

"John Doe"

p2p_trading_status
boolean
required

Is customer involved in P2P trading?

Example:

false

supporting_purpose_doc_url
array

array of urls for documents supporting purpose

Example:
[
"https://storage.example.com/uploads/example1.pdf",
"https://storage.example.com/uploads/example2.pdf"
]
relation_with_account_operator
string
Example:

"brother"

Response

Payin EDD submitted successfully

status
boolean
Example:

true

message
string
Example:

"Success"

data
object