Releases: xendit/xendit-php
Releases · xendit/xendit-php
6.0.0
- [Payment Methods] EWallet Channel Properties: New fields pending_return_url and promotion_label
- [Payment Methods] Direct Debit Channel Code: BNI enum changed to BNI_AUTOPAY
- [Payment Methods] Direct Debit Channel Properties New fields destination_account_id
- [Payment Methods] Card Channel Properties: New fields installment_configuration and merchant_id_tag
- [Payment Methods] New Error Code enums
- [Payment Requests] New XP Header with-split-rule
- [Payment Requests] Channel Properties: New fields pending_return_url and installment_configuration
- New channel codes for Direct Debit, Virtual Account, QR, and Card
5.0.0
- Add simulatePaymentRequestPayment API in payment-request
- Add pending_return_url field in ewallet payment method
4.3.0
- Add field channel_properties.cards.allowed_bins: array of string in Invoice Object
- Add field channel_properties.cards.installment: object in Invoice Object
4.2.0
- Fix RefundCallbackData Object, rename payment_request_id to payment_id
4.1.0
- Fix PaymentCallback failure_code field type to String
- Add MOMO, ZALOPAY, VIETTELPAY, VNPTWALLET, APPOTA to Invoice EwalletType
- Add BNC, HANA, MUAMALAT to Payment Request VirtualAccountChannelCode
- Add QRIS Payment Request QRCodeChannelCode
4.0.0
- Update Invoice field
amount
tofloat64
3.7.0
- Add PaymentCallback object in PaymentRequest module
- Add PaymentMethodCallback object in PaymentMethod module
- Add RefundCallback object in Refund module
- Add InvoiceCallback object in Invoice module
3.6.0
- Add account_number for Direct Debit
- Add TOUCHANDGO enum as new Ewallet Channel Code
- Add AMBANK enum as new Virtual Account Channel Code
3.4.0
- Support the for-user-id header for Invoices, Payouts and Payments API
- Add XENDIT_ENUM_DEFAULT_FALLBACK (value: UNKNOWN_ENUM_VALUE) for unknown enum fallback
3.3.0
- Fixed improperly labelled mobile number field for OVO tokenization on Payment Method
- Removed unused Payment Channels endpoint
- Added Customers API for creating Customers to be used with tokenization and account linking flows