Credentials on file (COF) different scenarios based on integration : Peach Payments

Credentials on file (COF) different scenarios based on integration Print

Modified on: Wed, 21 Jun, 2023 at 11:57 AM

Below you can see the different flows that the merchant will execute based on their integration and transactional flows.

Integration workflows

Registration in Secure eCommerce Gateway System

No	Use case	Supported	Integration	Endpoint	New COF request parameters
1.1	Registration during payment		COPYandPAY	/v1/checkouts	Cardholder is present createRegistration=true standingInstruction.mode = INITIAL standingInstruction.source = CIT challenge indicator: SCA mandated Due to PSD2 regulation, our platform automatically populates the challenge indicator with value 04 to mandate the challenge workflow during authentication process.
1.1	Registration during payment		Server-to-server	/v1/payments	Cardholder is present createRegistration=true standingInstruction.mode = INITIAL standingInstruction.source = CIT challenge indicator: SCA mandated Due to PSD2 regulation, our platform automatically populates the challenge indicator with value 04 to mandate the challenge workflow during authentication process.
1.2	Initial payment over Registration Subsequent payment over registration		COPYandPAY	/v1/checkouts	Cardholder is present createRegistration=true standingInstruction.type=UNSCHEDULED standingInstruction.mode = INITIAL standingInstruction.source = CIT challenge indicator: SCA mandated Due to PSD2 regulation, our platform automatically populates the challenge indicator with value 04 to mandate the challenge workflow during authentication process.
			One-click checkout	/v1/checkouts	Cardholder is present and selects one of the stored credentials registrations[0].id=abc1 registrations[1].id=abc2 standingInstruction.type=UNSCHEDULED standingInstruction.mode = REPEATED standingInstruction.source = CIT
			Server-to-server	/v1/payments	Cardholder is present createRegistration=true standingInstruction.type=UNSCHEDULED standingInstruction.mode = INITIAL standingInstruction.source = CIT challenge indicator: SCA mandated Due to PSD2 regulation, our platform automatically populates the challenge indicator with value 04 to mandate the challenge workflow during authentication process.
			One-click payment	/v1/registrations/{registrationId}/payments	Cardholder is present standingInstruction.type = UNSCHEDULED standingInstruction.mode = REPEATED standingInstruction.source = CIT
			Server-to-server	/v1/registrations/{registrationId}/payments	Cardholder is not present standingInstruction.type = UNSCHEDULED standingInstruction.mode = REPEATED standingInstruction.source = MIT
1.3	Initial recurring payment		COPYandPAY	/v1/checkouts	Cardholder is present createRegistration=true standingInstruction.type=RECURRING standingInstruction.mode = INITIAL standingInstruction.source = CIT challenge indicator: SCA mandated Due to PSD2 regulation, our platform automatically populates the challenge indicator with value 04 to mandate the challenge workflow during authentication process.
1.3	Initial recurring payment		Server-to-server	/v1/payments	Cardholder is present and uses customer's payment widget standingInstruction.type = RECURRING standingInstruction.mode = INITIAL standingInstruction.source = CIT challenge indicator: SCA mandated Due to PSD2 regulation, our platform automatically populates the challenge indicator with value 04 to mandate the challenge workflow during authentication process.
1.4	Repeated recurring payment		Server-to-server	/v1/registrations/{registrationId}/payments	Cardholder is not present standingInstruction.type = RECURRING standingInstruction.mode = REPEATED standingInstruction.source = MIT

Did you find it helpful? Yes No