Maniphest T136730

'order_id' is ambiguous. Call it 'merchant reference' whenever we generate it.
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	Ejegg
	Jun 1 2016, 6:53 PM

Tags

Referenced Files

None

Subscribers

Eileenmcnaughton

Description

We already have gateway_txn_id to store the ID generated by the payment processor. Refer to our ID in a way that makes it clear where it came from.

Related Objects

Mentioned In: T163947: Epic: Support and normalize multiple payment identifiers

Event Timeline

Ejegg created this task.Jun 1 2016, 6:53 PM

Restricted Application added subscribers: Zppix, Aklapper. · View Herald TranscriptJun 1 2016, 6:53 PM

• DStrine moved this task from Triage to Sprint +1 on the Fundraising-Backlog board.Jun 10 2016, 8:50 PM

• DStrine moved this task from Sprint +1 to Sprint +3 on the Fundraising-Backlog board.

• DStrine moved this task from Sprint +3 to Next on the Fundraising-Backlog board.Jul 18 2016, 7:15 PM

Ejegg mentioned this in T163947: Epic: Support and normalize multiple payment identifiers.May 10 2017, 10:43 PM

• DStrine moved this task from Next to FY 2022-2023 on the Fundraising-Backlog board.May 6 2019, 9:24 PM

XenoRyet moved this task from FY 2022-2023 to Unscheduled on the Fundraising-Backlog board.Mar 14 2023, 9:44 PM

@Ejegg does a merchant reference by any other name smell as sweet these days?

Eileenmcnaughton moved this task from Backlog to Code & data quality & maintainability on the Wikimedia-Fundraising-CiviCRM board.May 2 2023, 9:44 PM