C2C-US-1003-B-010010

Generated -- do not edit by hand. Regenerate: acd build C2C-US-1003-B-010010

Contents

1. What Is This?
1. SKU Breakdown
1. Capabilities
Channel References (UAT)
1. Merchant Configuration
1. Configuration Details
Step 1: Merchant
Step 2: Terminal Config
Step 3: merchantPaymentGateway array
1. Open Items (2 fields)
1. See Also

1. What Is This?

Elavon Microservice (MS) product code for C2C Ecommerce (C2C) in the US region.

Active payment methods: Token + Ecommerce + MPI / 3DS. 3DS / MPI authentication included.

Default transaction flows: sale, auth, capture, void, refund

Business context: This SKU is intended for C2C ecommerce merchants operating in the US that require the Elavon MS integration with token-based checkout and an alternate implementation variant.

Characteristics

Characteristic	Value
Architecture	Microservice (MS)
3DS / MPI	No
Tokenization	Yes
Bank Card	No
Ecommerce (HPP)	Yes
QR Code	No
Gift Card	No
Partial Auth	Yes

2. SKU Breakdown

+-----+----+------+----+--------+
| C2C | US | 1003 | B  | 010010 |
+-----+----+------+----+--------+

Segment	Value	Meaning
Industry	`C2C`	C2C Ecommerce (reference)
Region	`US`	(reference)
Solution	`1003`	Elavon / MS (reference)
Variant	`B`	(author meaning in reference/sku-naming.md)
Capabilities	`010010`	PM1, PM4 active (reference)

3. Capabilities

Payment Methods

PM Slot	Payment Method	Active
PM0	Bank Card	No
PM1	Token	Yes
PM2	QR MS	No
PM3	QR GS	No
PM4	Ecommerce	Yes
PM5	Gift	No
PM99	MPI / 3DS	Yes

Product Family — Solution `1003`

SKU	Industry	Variant	PM1	PM4	3DS
C2C-US-1003-A-010010	C2C	1003-A	Yes	Yes	No
C2C-US-1003-B-010010	C2C	1003-B	Yes	Yes	No

Channel References (UAT)

Channel IDs from the UAT values file. SIT and PROD IDs belong in data/channels/ (not yet created).

Purpose	Channel ID	Var
Ecom Processing Channel	`20379`	`ecom_processing_channel`
Ecom Widget Channel (HPP)	`20495`	`ecom_widget_channel`
Merchant Token Channel	`20389`	`merchant_token_channel`
MOTO Processing Channel	`20379`	`moto_processing_channel`
MPI / 3DS Channel	`20379`	`mpi_processing_channel`

4. Merchant Configuration

Configure the following MGMT objects in order. Each row = one API call.

Step	MGMT Object	Table	Required	Notes
1	Merchant	`merchant`	Y	Step 1
2	Terminal Config	`terminalConfig`	Y	Step 2
3	merchantPaymentGateway	`merchantPaymentGateway`	Y	[ ] PM0 [x] PM1 [ ] PM2 [ ] PM3 [x] PM4 [ ] PM5 [x] PM99

Secret fields -- cells marked <secret> contain credentials or PII. Never commit actual values to source control. Supply via your secrets manager or provisioning vault.

5. Configuration Details

Columns: Key = provisioning identifier | MGMT Field = API body field name | Sample = UAT value (seed; verify before PROD) | Source = origin of the value

Step 1: Merchant (`merchant`)

Key	MGMT Field	Type	Required	Sample (UAT)	Notes
`MERCHANT_NAME`	`merchantName`	string	Mandatory	`default name`	Merchant display name
`BUSINESS_SYSTEM`	`bizSystemId`	enum	Conditional	`000010`	Business system ID (see business_systems lookup) Lookup: `{{baseUrl}}/v1/list/bizSystem`
`SKU_STAMP`	`extData10`	string	Conditional	--	SKU stamp = the merchant<->docs join key (currently UNWIRED in templates)

Step 2: Terminal Config (`terminalConfig`)

Key	MGMT Field	Type	Required	Sample (UAT)	Notes
`ACQUIRER_TID`	`channelTerminalId`	string	Mandatory	`<secret>` (supply via secrets manager)	Acquirer Terminal ID (TID). NOTE: per-terminal in 3DS template, per-merchant in non-3DS
`TRANS_TIMEOUT`	`extData8`	int	Conditional	`40000` (default)	[unconfirmed] Transaction timeout (ms). 3DS template default 40000 but deployments use 180000 — confirm

Step 3: Merchant Payment Gateways (`merchantPaymentGateway`) -- Array

2 entries required. Provision in the order listed below.

Entry 1 -- PM4 -- Ecom Processing

Key	MGMT Field	Type	Required	Sample (UAT)	Notes
`ECOM_HOST_URL`	`extData1`	url	Mandatory	`<secret>` (supply via secrets manager)	Ecom processing host URL
`ECOM_EXTDATA3`	`extData3`	string	Optional	--	[unconfirmed] PURPOSE UNKNOWN — confirm with Elavon integration owner
`CARDHOLDERNAME_CONF`	`extData7`	enum	Conditional	`mandatory`	Cardholder name capture rule Values: `mandatory`, `optional`, `disabled`

Entry 2 -- PM99 -- MPI / 3DS

Key	MGMT Field	Type	Required	Sample (UAT)	Notes
`MPI_HOST_URL`	`extData1`	url	Mandatory	`<secret>` (supply via secrets manager)	MPI host URL (3DS SKUs only)

6. Open Items -- Needs Sign-off

Fields marked confirm: true in the schema. Verify before production.

TRANS_TIMEOUT / extData8: Transaction timeout (ms). 3DS template default 40000 but deployments use 180000 — confirm
ECOM_EXTDATA3 / extData3: PURPOSE UNKNOWN — confirm with Elavon integration owner

7. See Also

Page metadata

| | | |:---|:---| | SKU | `C2C-US-1003-B-010010` | | Schema source | `schema/elavon.yaml` | | Values source | `values/` (see `_VALUES_MAP` in pr