One Step Payment - create Payment - clarification required.

[psidana1983]

Team ,

Can you please help me with inputs on below points related to API

1. Is it mandatory to implement the Asynchronous use case . if it is not mandatory then , can I remove Webhook parameters from – createPayment API (1 step payment)
2. In the createPayment API – what is the difference between clientCorrelator and merchantIdentifier , which field shall we use for client profileID mapping
3. In the schema – request field clientCorrelator is optional but in the description it is written as “This field SHOULD be present.” So I am confused if it is mandatory or non-mandatory .
4. What is the difference between paymentItem and chargingInformation object , as both has the same fields , also how to decide which one to use.
5. As per the given description – request field phoneNumber is optional and should be inferred from the token . So here , are you referring to JWT token ? Currently we are using Opaque tokens so can’t we make phone number field as mandatory ? or it mandatory to implement JWT token and infer phone number only from the token . We currently have OAuth 2.0 Implemented with Client Credential Flow . Here , we are not capturing user phone number in the token so please update if it is mandatory to implement it to get certified or I can continue with OAuth 2.0 based implementation.
6. What does validatePayment API do ? Is it mandatory to implement it for certification ?
7. Which field(s) to use for identifying individual merchant and service? merchantIdentified, serviceid, productid fields appear as optional in the specifications so which other mandatory fields can we rely on for this purpose?

[psidana1983]

hi Team , Any updates please ?

Regards Prashant Sidana

[psidana1983]

Hi Team , Below I am sharing the points discussed and agreed in a meeting on 26th June . Please review acknowledge

• It was confirmed by CAMARA representative that, for the certification Validate API and Async flows of all the APIs are not mandatory as these are optional. Mandatory use cases are only one step payment, 2 step payment with reserve, commit and cancel along with inquiry API’s. • As per UAE Tax law it is mandatory for operator to know type of VAT, but CAMARA API’s does not support VAT type (in case of no vat or with vat), API’s only have tax included or not included (as optional). Additionally, as per TDRA regulations for any app store partners, operator should have control on minimum and maximum amount that can be deducted. These regulatory compliances are not directly supported in the CAMARA API’s but as per yesterday’s discussion and agreement, operator can make use of any optional parameter to mark it as mandatory while implementing the specification and keep these business configurations and control inside operators’ business logic based on the mutual agreement with operator and partner. • CAMARA API’s does not support REFUND which in our case is must . As per our yesterday’s forum discussion, CAMARA would release another version in near future which will have REFUND and other changes. • As per CAMARA representative, it has been confirmed that for the certification, only mandatory API parameters are required, and depending on the business requirements, operator has full control to make any optional parameter as mandatory either in request or response, provided it is mutually agreed between partner and operator. • Depending on the agreement and business case with partner, handling of error descriptions, status and codes can also be customized over and above provided standard errors, and this will not affect standardization. • As per the discussions, operators are free to choose and make any one or more currencies as mandatory. For UAE, only AED is supported, and it is aligned to have only AED deductions with partners.

regards Prashant Sidana

[psidana1983]

hi Team , Any updates on my questions please .

Regards Prashant Sidana