Identify if the payment is one time payment or recurring payment

[mohamedsaeedstc]

Hello,
It's needed to have a flag that identify if this payment one time payment or it's a recurring payment, this flag can be used to trigger second factor authentication for customers or no "OTP Screen" before complete the payment.
For recurring payment, OTP Screen will not be required.

Also, during getting customer consent this flag also is required to notify the customer as part of "Scope" this consent will grant for this merchant this time only or for future use. In addition to that, it will be reflect in Token lifetime.

Thanks
Mohamed

[PedroDiez]

Thanks @mohamedsaeedstc will mention this in today's meeting.
I am also addressing this internally, in order to see Business Priority in TEF and the prioritization of this feature in GSMA OGW

[PedroDiez]

Agreed to have aligment and Business guidance from GSMA OGW Product first

[PedroDiez]

As commented in 20/DEC meeting:

• Every Operator to check internally priority of this feature
• Also welcome Use Cases to understand requirements

[PedroDiez]

02/OCT:
@mohamedsaeedstc Is still there interest on this feature?
Please, if so, can you elaborate a more detailed business proposal about it? (maybe a high level PPT / diagram showing how it is initially expected to behave)

After today's discussion for recurring payments it is not only the fact of indicating whether payment is one-time/recurrent, but also providing recurrency period, how to managed its ending,...

[mohamedsaeedstc]

@PedroDiez Sorry for the late response. Yes this usecase is one of the existing use cases here.
Yes agree with you about more informaiton will be available about recurrency period, end date ..etc.
This put dependency between this API (recurring payment) and consent process, becuase we should notifiy the customer about the recurrening payment details.
So, is this recurring payment will be a separate API?

[PedroDiez]

@mohamedsaeedstc No problem.
We would first need the business proposal from your side.

Maybe you can elaborate some material an expose within the WG, so it can be analyzed by the WG in order to think the best way to manage it

[PedroDiez]

2024-11-27: WG Output: Out of scope for MetaRelease Spring 25. Set to backlog