Payment and Installment Options
Pleated Blind takes as basis that payment transactions are carried out in a clear, secure and traceable manner. Available methods are shown on the order screen. In card transactions, installment options may vary according to bank and infrastructure. In remittance, EFT and FAST payments, collection is verified additionally. Additional fees are explained visibly before payment. Custom measurement production process may not be started before payment record is finalized. This policy regulates payment and installment principles.
1. Purpose of the Payment Policy
This policy explains the payment methods that can be used in Pleated Blind orders. The text covers card payment, remittance, EFT, FAST and installment options. Each method is evaluated according to its own technical rules. Banks' current practices are also taken into account.
Pleated blind products are mostly prepared custom-size. Fabric cutting and profile transactions may be made according to order. For this reason, collection confirmation is important. Payment flow may directly affect production planning.
The table below separates the basic payment concepts from each other. The user can see the nature of the relevant method before the transaction.
| Concept | Description | Application Equivalent |
|---|---|---|
| Card Payment | Collection made via bank card or credit card. | Virtual POS or payment institution infrastructure |
| Single Payment | Collection of order amount with single transaction. | Cash transaction on card payment screen |
| Installment Payment | Division of order amount with terms offered by card provider. | Options shown according to bank and card type |
| Remittance | Money transfer within the same bank. | Direct sending to bank account |
| EFT | Money transfer between different banks. | Sending within bank's transaction rules framework |
| FAST | Method that can provide instant transfer under suitable conditions. | Payment within amount limits supported by bank |
| Deposit | Part of order amount collected before production. | Applied only in explicitly agreed transactions. |
Not every payment method may be offered at the same time. Available options must also be shown on payment screen.
2. Available Payment Methods
Pleated Blind may offer payment methods suitable for operational structure. Technical infrastructure and collection rules are different for each method. Customer must be able to see available options before order is completed. Methods not offered must not be promised.
The table below shows how payment methods will be verified before publication. Rows not actually used must be removed.
| Payment Method | Usage Status | Description |
|---|---|---|
| Credit Card | [ACTIVE] | May be used with single payment or suitable installment options. |
| Bank Card | [ACTIVE] | May be used under conditions supported by infrastructure. |
| Remittance | [ACTIVE] | Sending may be made to published bank account. |
| EFT | [ACTIVE] | May be used in payments between different bank accounts. |
| FAST | [ACTIVE] | May be preferred within limits supported by bank. |
| Cash on Delivery | [NOT USED] | If not offered, must be removed from text. |
| In-Store Payment | [ACTIVE] | May be shown if physical sales point exists. |
Customer may only benefit from methods that appear active on payment screen. If technical error is seen, support record must be created.
3. Card Payment Security
Card payments are carried out via used virtual POS or payment institution infrastructure. Card information must be processed via secure connection. SSL certificate must be kept active. 3D Secure support must be used in transactions where possible.
Pleated Blind may use payment provider's transaction screen directly or in integrated manner. Card number must not be sent via message. CVV information must not be shared. SMS verification code must not be given to anyone.
The list below shows the basic security steps that must be preserved during card payment. Users must not pay attention to unusual redirects.
- Check the domain name in the address bar.
- Verify that HTTPS connection is active.
- Do not share your card number via message.
- Do not send your CVV code to third parties.
- Do not share SMS verification code with anyone.
- Do not install remote access application.
- Do not click suspicious links.
- Check payment result only from official screen.
When suspicious transaction is noticed, contact must be established with bank without delay. Written notification may also be sent to Pleated Blind.
4. 3D Secure Verification
3D Secure may provide additional verification in card payments. Verification step may be offered to card owner by bank. User completes the transaction via their own bank screen. Verification code is not shared with Pleated Blind personnel.
Not every card or bank may use the same verification flow. Bank may apply different method according to risk evaluation. If transaction is rejected, must be discussed with bank. Verification code must only be entered into bank's secure screen.
The table below explains 3D Secure transaction stages. Technical flow may vary according to payment provider.
| Stage | Description | What the User Must Do |
|---|---|---|
| Card Information Entry | Card information is written to secure payment screen. | Check domain name and connection. |
| Bank Verification | Bank may offer additional verification step. | Enter code only into bank screen. |
| Transaction Result | Payment ends as successful or unsuccessful. | Check the result screen. |
| Order Record | Successful collection is matched with order. | Keep the order number. |
Unnecessary repeated attempts must not be made after unsuccessful transaction. Contact may be established with bank or support unit.
5. Displaying Installment Options
Installment options may vary according to bank and card type. Virtual POS provider may show current options on payment screen. Same term may not be offered for every card. Different limits may be applied on corporate cards.
Pleated Blind must not use unverified installment counts as fixed promise. Options may change in campaign periods. Bank decisions may be reflected on payment screen. Current option on screen is the basis.
The table below explains how installment visibility will be managed. Definite options must only be pulled from live payment screen.
| Card Type | Possible Option | Definite Information Source |
|---|---|---|
| Individual Credit Card | Single payment or suitable installment options | Current bank options on payment screen |
| Corporate Credit Card | Options permitted by card provider | Virtual POS and bank verification |
| Bank Card | Single payment or method supported by infrastructure | Payment provider screen |
| Foreign Card | Single payment or limited use | Card provider and payment infrastructure |
Installment selection must be visible before order approval. A different term must not be promised later.
6. Installment Limits and Bank Rules
Credit card installments may be limited by legislation and bank policies. General limits may vary according to product category. Lower term may be applied in some expenditures. Installment may be completely prohibited in some areas.
Pleated blind products' classification on payment screen must be verified with virtual POS provider. Wrong category must not be used. Bank campaigns must also be examined. Current regulation must be the basis.
The list below lists the areas that must be checked before installment options are shown. Technical and legal check must be made together.
- Merchant business category code
- Correct classification of product group
- Virtual POS provider's current settings
- Individual card installment options
- Corporate card limits
- Bank campaigns' validity dates
- Term difference rates if any
- Foreign card restrictions
Installment options may be updated periodically. Fixed campaign texts must be checked at regular intervals.
7. Term Difference and Additional Fees
Installment payment may create term difference in some cases. If there is additional fee, it must be shown clearly before payment. Total amount must be visible by customer. Hidden commission must not be applied.
Cash price and installment total may differ. If such difference exists, each option must be shown in separate row. User approval must be obtained. Additional fees not approved must not be charged to customer later.
The table below explains the price fields that must be shown on payment screen. Real values must be taken from payment infrastructure.
| Price Field | Description | Display Time |
|---|---|---|
| Product Price | Total price of products subject to order | Cart and payment screen |
| Shipping Fee | Delivery expense if any | Before order approval |
| Mounting Fee | Service fee requested separately if any | Before selection and approval |
| Term Difference | Additional amount arising from installment option if any | During installment selection |
| Grand Total | Final amount the customer will pay | Before payment obligation arises |
Total price must be shown in clear and understandable manner. If calculation error is seen, transaction must not be completed.
8. Remittance, EFT and FAST Payments
If payment will be made via bank transfer, published account information must be used. IBAN and account owner must be checked together. Order number must be written in description field. Transfer record is verified over bank movements.
Sending receipt may speed up the check. However, receipt alone does not mean definite collection. Amount must reflect to account. Wrong IBAN transactions are evaluated separately.
The list below shows the steps that must be followed in bank transfer. Customer must re-check account information before transaction.
- Open the current IBAN information.
- Check the account owner title.
- Write your order number in the description field.
- Compare the amount with order summary.
- Complete the transfer.
- Keep the receipt.
- Send written notification if necessary.
- Check the collection confirmation.
Custom production start must not be assumed before collection confirmation is obtained. Order status may be notified in writing separately.
9. Payment Verification
Payment transaction is finalized when the relevant collection record is reflected to system. In card payments, virtual POS result is taken into account. In bank transfers, account movements are checked. Technical delays may be evaluated separately.
Unsuccessful payment does not complete the order. Pending transaction may be examined separately. If duplicate collection is seen for the same order, accounting record is opened. Collection record is the basis.
The table below explains the meaning of payment statuses. Expressions on order screen must be compatible with technical infrastructure.
| Payment Status | Description | Possible Transaction |
|---|---|---|
| Successful | Collection verified by infrastructure. | Order record may be updated. |
| Unsuccessful | Collection not completed. | Contact may be established with bank or payment provider. |
| Pending | Transaction result not yet finalized. | Additional verification may be made. |
| Incomplete Payment | Sent amount is lower than order price. | Remaining balance is notified. |
| Excess Payment | Collected amount exceeds order price. | Accounting review is made. |
| Duplicate Payment | Repeated collection seen for the same order. | Refund or offset is evaluated. |
Transaction result may be notified to customer via appropriate channel. Support record may be created if necessary.
10. Relationship Between Custom Measurement Production and Collection
Pleated blind products may be prepared according to measurements reported by customer. Fabric and profiles may be processed according to order. The use of cut products for other customers may be limited. This situation makes payment verification important.
Custom production plan may be created after collection is completed or agreed deposit is verified. Order summary is also checked separately. Written confirmation of measurements may be needed. Making payment does not mean wrong measurement is automatically corrected.
The table below shows the effect of collection status on production plan. Fields not overlapping with actual practice must be removed.
| Collection Status | Possible Production Status | Description |
|---|---|---|
| Payment Not Received | Production plan may not be created. | Collection record is awaited. |
| Deposit Verified | Planning may be made according to order conditions. | Deposit practice must be explained in writing. |
| Full Payment Verified | May proceed to production plan. | Measurements and product preferences are also checked separately. |
| Remaining Balance Exists | Transaction may be put on hold. | Remaining amount may be notified to customer. |
| Collection Under Review | Production start may be postponed. | Suspicious or unmatchable transaction is checked. |
Production start and payment conditions must be kept visible on order screen. Written confirmation may be given to customer.
11. Deposit Practice
If deposit is to be applied, rate or amount must be explained before ordering. Remaining balance date must be clear. Its relationship with production start must be shown. Indefinite payment plans must not be used.
Deposit conditions may not be the same in every order. Product nature and project scope may be taken into account. Written payment summary must be presented to customer. Payment plan must be clear.
The table below shows the fields that can be filled if deposit is applied. If deposit is not used, this section must be removed.
| Deposit Field | Description |
|---|---|
| Deposit Rate | [PERCENTAGE OR FIXED AMOUNT TO BE ADDED] |
| Remaining Balance | [PAYMENT TIME TO BE ADDED] |
| Production Start | [MUST BE EXPLAINED AS AFTER DEPOSIT OR FULL PAYMENT] |
| Payment Method | [CARD / REMITTANCE / EFT / FAST] |
| Written Confirmation | [ORDER SUMMARY AND PAYMENT PLAN MUST BE SHARED] |
Deposit conditions do not eliminate customer's legal rights. Every transaction is evaluated with its own records.
12. Protection of Card Information
Card information must only be entered into secure payment screen. Card number must not be shared via phone, email or WhatsApp. Front or back side of card must not be sent. Verification code must not be transmitted.
Pleated Blind personnel does not request bank password. Does not request internet banking access. Does not have remote connection application installed. Suspicious requests must not be paid attention.
The list below shows the information that must absolutely not be shared. This information must remain only in user's own security.
- Full card number
- CVV security code
- Card password
- Internet banking password
- SMS verification code
- Mobile banking approval notification
- Remote access application information
- Single-use bank codes
When suspicious request is seen, transaction must be stopped. Bank and Pleated Blind support unit must be informed.
13. Unsuccessful Payment and Technical Problems
Payment transaction may not be completed due to technical reason. Card limit may be insufficient. Bank security check may reject the transaction. Virtual POS may give temporary error.
Customer must not repeat the same transaction unnecessarily. Pending collection must be checked. Bank movements must be examined. Support request must be created if necessary.
The table below shows the unsuccessful payment reasons and recommended steps. Definite reason may be determined by bank or payment provider.
| Possible Problem | Description | Recommended Transaction |
|---|---|---|
| Insufficient Limit | Card limit may not cover transaction amount. | Contact may be established with bank. |
| 3D Secure Error | Verification may not have been completed. | Bank screen must be re-checked. |
| Card Restriction | Internet shopping may be closed. | Card settings must be checked from bank. |
| Technical Interruption | Virtual POS may not work temporarily. | May be tried again later. |
| Pending Transaction | Collection result may not be finalized yet. | Support must be received without duplicate attempt. |
Bank account or card movements must be examined for transaction that appears unsuccessful. If there is duplicate collection, written notification must be made.
14. Excess or Duplicate Collection
Multiple collections may be seen for the same order. Excess amount may have been drawn. In such cases, payment records are compared. Bank movements and virtual POS logs may be examined.
If refund is needed, payment source must be verified. Refund method may be notified in writing. Bank transaction times may be applied separately. Suspicious refunds are not made before verification is completed.
The table below shows the records that can be used in duplicate collection review. Customer must keep relevant documents.
| Record | Review Purpose | Possible Source |
|---|---|---|
| Order Number | Matching collection with order | Order screen or email |
| Bank Movement | Verifying draw count and amount | Card or account statement |
| Virtual POS Record | Examining transaction result technically | Payment provider |
| Collection Date | Comparing duplicate transactions | Bank and order records |
Necessary correction may be made as a result of review. Process may be notified to customer in writing.
15. Invoice and Payment Record
Payment record and invoice record may be connected to each other. Collection method may be processed into accounting system. Invoice information must be entered correctly. Title and tax information must be checked in corporate purchases.
The list below shows the fields that must be verified before invoicing. Wrong information may cause delay.
- Name and surname
- Corporate title
- Tax office
- Tax number
- Invoice address
- Email address
- Order number
- Payment method
Invoice information must be checked before payment. Written correction request may be submitted for erroneous records.
16. Payment Notification Channels
Payment and installment requests may be submitted via the following communication channels. Written methods facilitate record creation. Order number must be specified. Card information must not be shared in any way.
The table below shows the communication channels that can be used. The method appropriate to the nature of the request must be selected.
| Channel | Information | Purpose of Use |
|---|---|---|
| Brand | Pleated Blind | Payment and installment transactions |
| Phone | +90 540 336 3873 | General information |
| +90 540 336 3873 | Written notification and receipt sharing | |
| info@pliseperde.com | Official payment notifications | |
| Address | Esenyalı Mah. Edebali Cad. No:13/C, 34903 Pendik/Istanbul | Written applications |
Only general information must be obtained via phone. Sensitive financial information must not be shared in written channels either.
17. Sample Payment Notification
The text below shows the sample notification that can be used after remittance or EFT. Fields in brackets must be filled with transaction information.
Sample notification: "I made the payment of [AMOUNT] regarding my order numbered [ORDER NUMBER] on [DATE]. I am sending the receipt for your review. I request that the collection confirmation be notified to me in writing."
Clear notification facilitates accounting check. Unnecessary bank data must not be shared in message.
18. Policy Updates and Entry into Force
Pleated Blind may update payment infrastructure according to operational needs. Virtual POS provider may change. Installment options may be renewed according to banks. Unused methods must be removed from text.
Substantial changes must be reflected on payment screen. Current amounts must be shown before order approval. Old campaign texts must be removed. Current options on live payment screen must be the basis.
The table below shows the basic version information regarding the document. Records must be changed when updated.
| Document Information | Value |
|---|---|
| Document Name | Payment and Installment Options |
| Brand | Pleated Blind |
| Official Trade Title | [OFFICIAL TRADE TITLE TO BE ADDED] |
| Virtual POS Provider | [PAYMENT PROVIDER TO BE ADDED] |
| Entry into Force Date | June 12, 2026 |
| Version | 1.0 |
| Contact Email | info@pliseperde.com |
This policy must be kept consistent with real payment infrastructure and live bank options. Unverified installment campaigns must not be published.