Change Log
- Added support for sending customer data in checkout endpoint payload, allowing pre-populate customer info at Order Summary page
- Fixed issue related to the customer verification process
- Added validation for monthlyIncome value in apply endpoint. Now monthlyIncome value should not be greater than $50000.
- Fixes in application/verification flow
- Added query parameters to filter transactions by date
- Optimized apply endpoint schema, fields like
employmentInformation.name
,employmentInformation.phone
are not required to create a customer application - Added support for creating a user without password. In this scenario a temporary password is created and an email is sent to the customer to provide a new password.
- Added support for confirming a shipment without tracking number
- Added
decision.status
field in GET /users/me response. The possible values are (approved, denied, pending and error). The fielddecision.approved
is going to be deprecated in future versions. - Added support for transport
all
in endpoint POST /users/{userId}/send-passcode. It sends the passcode to all available transports for a customer - Added quantityByStatus support in GET /transactions and GET /transactions/{id} endpoint. It groups the item quantity by status for all items with the same sku in the order.
- Updated customer schema (added customer info, transactions and decision creation date) in /users/me endpoint
- Set 15 days as default delivery date for all transactions
- Improved checkout validation for payload with multiple items using the same SKU
Last modified 3yr ago