---
title: "E-Receipt API"
method: POST
path: "/?ereceipt"
---

# E-Receipt API

`POST /?ereceipt`

## Request body

- object
  - `appid` string, required — Merchant APP ID (Alphanumeric - Length of 32 chars and special chars $@%#)
  - `appkey` string, required — Merchant APP KEY (Alphanumeric - Length of 32 chars and special chars $@%#)
  - `epi` string, required — EPI is an end point identifier, Identify the device on valor infrastructure, it's a 10 digit number starts with 2
  - `txn_type` string, required — Transaction type always should be set as 'eReceipt'
  - `phone` string — Customer phone number- 10 digit Numeric (Ex: 5247896523)
  - `receipt_type` integer, required — 0 - Merchant Copy & 1 - Customer Copy
  - `txn_id` string, required — A unique response transaction id from the response of a sale transaction (Numeric - Length of 20 chars)
  - `email` string — Customer email id - Varchar (Ex: test@domain.com, Max length of 50 chars)
  - `child_epi` string — If the merchant has multi-MIDs, they need to send both the child EPI and the parent EPI in the EPI request

## Response `200`

200

- object

## Other responses

- `400` — 400

---

[API](https://skmtc.net/valorpaytech/apis/ecommerce-api.md) · [All operations](https://skmtc.net/valorpaytech/apis/ecommerce-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/valorpaytech/ecommerce-api/revisions/c6468b606325/schema)