2. Cards
It is recommended that you only pull the saved card data from your servers (Back-End). It is not recommended to directly access your applications (End User).
List Cards
GET
{{Base Address}}/paywall/card
Important: Card transactions are highly secure transactions. Therefore, you need to send the 'apikeyprivate' and 'apiclientprivate' parameters in the 'Header' field.
The parameters (HEADER) to be sent to the service are as follows:
Parameter (Headers) | Type | Required | Description |
---|---|---|---|
apikeyprivate | string | Yes | Private Key that you have obtained from the merchant panel. |
apiclientprivate | string | Yes | Private Client that you have obtained from the merchant panel. |
relationalid1 | string | Yes | Associated first value of registered card. |
relationalid2 | string | No | Associated second value of registered card. |
relationalid3 | string | No | Associated third value of registered card. |
The parameters returned from the service are as follows:
Parameter | Type | Description |
---|---|---|
Name | string | Nickname given when adding a card |
CardBin | string | BIN information of the card |
CardLastFour | string | The last 4 digits of the card |
CardNumber | string | Masked card number. You can list them on their screen |
Expired | boolean | Indicates that the expiry date of the card has passed/hasn't passed. If it is true, no payment can be made with that card |
CardTypeId | int | Indicates the brand of the card. MasterCard, Visa etc |
CardType | string | Returns the card's brand as a string |
UniqueCode | string | It is the card ID that should be used when a card payment is requested. This information changes periodically. Therefore, the UniqueCode information of the registered card should not be stored. A card list must be obtained from Paywall before each payment |
Last updated