4. Update Card
It is recommended to perform the process of updating a registered card only through your servers (Back-End). Direct access from your applications (End Users) is not recommended.
Update Registered Card
PUT
{{Base Adres}}/paywall/card
Simply making a request to the address provided above will suffice. You can use the 'Base Address' as you wish for both the Test environment and the Production environment.
The parameters (HEADERS) that need to be sent to the service are as follows:
apikeyprivate
string
Yes
The Private Key obtained from the merchant panel.
apiclientprivate
string
Yes
The Private Client obtained from the merchant panel.
The parameters (BODY) that need to be sent to the service are as follows:
PartnerBased
bool
No
This is applicable to cards registered under the partnership.
PartnerIdentity
string
Yes/No
This applies to cards registered within the scope of the partnership.
RelationalId1
string
Yes
The unique information associated with the card.
RelationalId2
string
No
The second unique information associated with the card.
RelationalId3
string
No
The third unique information associated with the card.
UniqueCode
string
Yes
The unique information (identifier) of the stored card.
Month
int
Yes
The expiration date (Month) of the stored card to be updated.
Year
int
Yes
The expiration date (Year) of the stored card to be updated.
The parameters for the response message sent from the service after the transaction are as follows:
ErrorCode
int
It reports the result of the transaction. It returns '0' if the transaction is successful, and '1' otherwise.
Result
string
If the transaction is successful, it returns 'true'; otherwise, it returns 'false'.
Message
string
It reports the transaction result message.
Body
object
If the transaction is unsuccessful, this is the detail object for the error.
Sample Code:
Last updated