1. Generate
The common payment page creation flow is the preferred method when you do not want to receive card information through your site/app.
Generate Common Page Payment
POST
{{Base Adres}}/api/paywall/checkout/generate
Important: In order to use this service, you need to send the 'apikeypublic' and 'apiclientpublic' parameters in the 'Header' field. PaymentAPI Address
Parameter | Type | Required | Description |
apikeypublic | string | Yes | The Public Key you have obtained from the merchant panel. |
apiclientpublic | string | Yes | Public Client that you have obtained from the merchant panel. |
Parameters that should be sent to the service are as follows:
Parameter | Type | Required | Description |
---|---|---|---|
UniqueCode | string | Yes | Tracking/order/cart code on your side of the Payment |
Amount | decimal | Yes | Total amount |
CurrencyId | int | Yes | |
CallbackSupport | bool | Yes | Successful payment results are POST as callback to an address |
CallbackAddress | string | No | Address to send callback on successful payment results |
InstallmentSupport | bool | Yes | Do you support payment installments? |
SuccessBackUrl | string | Yes | URL address to be sent if the operation is successful |
FailBackUrl | string | Yes | URL address to be sent if the operation is fail |
Force3D | bool | Yes | Force user to "Secure Checkout" on common checkout page? |
ShowProduct | bool | Yes | Should the products subject to payment be listed on the common payment page? |
ExpireDateTime | datetime | No | The lifetime of the common payment page. It can also be determined by you, if not determined, it is determined as 10 minutes. |
Products | List<Product> | No | Product information subject to payment (Listed on common checkout page if allowed) |
Customer | Customer | No | Customer information subject to payment (It is not displayed on the common payment page. It is used in reporting) |
CardWallSupport | bool | No | You can use it to enable support for registered cards on the common payment page. |
CardWallRelationalId1 | string | No | The unique information required for associating the card. |
CardWallRelationalId2 | string | No | The second unique information required for associating the card (all information must be sent during listing). |
CardWallRelationalId3 | String | No | The third unique information required for associating the card (all information must be sent during listing). |
Products parameter above:
Parameter | Type | Required | Description |
---|---|---|---|
ProductId | string | No | ID of your product on your system |
ProductImage | string | No | URL of your product image |
ProductName | string | No | Your product name |
ProductCategory | string | No | Category of your product |
ProductDescription | string | No | Description of your product |
ProductAmount | decimal | No | The amount of your product |
Customer parameter above:
Parameter | Type | Required | Description |
---|---|---|---|
FullName | string | No | Customer name/surname |
Phone | string | No | Customer phone number |
string | No | Customer e-mail | |
Country | string | No | Country |
City | string | No | City |
Address | decimal | No | Full address |
IdentityNumber | string | No | Individual Customer |
TaxNumber | string | No | Corporate Customer |
An example JSON to be sent to the service is as follows:
The parameters returned from the service are as follows:
Parameter | Type | Description |
ErrorCode | int | Error code. If the operation is successful, it returns '0'. |
Result | bool | Returns True or False. Transaction successful request returns 'true' |
Message | string | If the operation is wrong, this is the message about the error, it provides language support according to the local parameter. |
Body | string | Returns the payment link under the link parameter |
An example JSON:
Last updated