In the Get international payments configuration (GET /v3/vendors/configuration/international-payments) API response, we now provide the description information for more fields objects in the validations array. This information can help you correctly set the required information in your API request.

For example, when you want to add a Brazilian vendor bank account, the "name": "accountNumber" fields object now includes the "description": "IBAN" information. This confirms that you must set the bank account IBAN value as the accountNumber in your API request.

See Create an international vendor for more information.

In the Get list of payments (GET /v3/payments) and Get payment details (GET ​​/v3/payments/{paymentId}) API response, we have introduced the vendorName field. You can now get the vendor name for each payment with these endpoints.

See GET /v3/payments in the API reference for more information.

Features

User verification widget improvements

Based on the BILL API response, we have improved error handling in the user verification widget.

Onboarding widget improvements

On the KYC/KYB screen, we have improved the pre-population logic for the full name of the organization owner in the Owner name field.

Bug fixes

User verification widget

• We learned that a spinner would intermittently go beyond the bounds of the widget. We have now fixed this issue.
• We learned that the camera was preventing the user from uploading documentation for user verification. We have now fixed this issue.

Manage funding widget

The user that has added a bank account must also be the one that verifies the bank account. We learned that for an unverified bank account, we would show the Verify link to all the users on the bank account details screen. We have now fixed this issue. When a user on the bank account details screen is not the one that added the bank account, we now display a message stating that the account is waiting for verification by the user who added the account.

Features

Add funding widget improvements

We now inform the user when a funding method is successfully added.

Manage funding widget improvements

On the bank account details screen, we have replaced the Back to payment methods button with a Back to payment methods link. This update makes it clear that the UI element is for navigation.

User verification widget improvements

We have improved error handling in the user verification widget. When the user receives a an error from the third-party questionnaire service, we now direct the user to upload the required documents for verification.

We have introduced a new API endpoint for getting an invoice payment link.

You can now get a payment link based on the invoice and customer information you provide. You can send the invoice payment link to your customer for getting paid by the customer. With this link, the customer can complete the invoice payment without the need to set up a BILL account.

We have introduced a set of API endpoints for received payment operations. You can now get and list payments that your BILL organization has received by customers.

We have introduced a set of API endpoints for credit memo operations. You can now create credit memos for adjusting the invoice amount owed by customers.

In addition, you can apply credit memo amounts to invoices. In the create and update invoice operations, you can now set the new creditAmount field in your request as the credit amount applied to an invoice.

See Credit memos for more information.

The webhook notification payloads for all bill, vendor, bank account, and card account events now include all the response fields. For example, if you have subscribed to the vendor.created event, the payload for each related notification will now include the response fields for each created vendor.

All the webhook notification payload samples have been updated in the documentation.

• Bill notification payloads
• Vendor notification payloads
• Bank account notification payloads
• Card account notification payloads

In addition, the vendorName field is now available in all the bill webhooks. If you have subscribed to the bill.updated, bill.archived, or bill.restored events, the vendorName field is available in each payload.

When you create or update an item, you can now set the percentage field as the item tax percentage. You can set this field for a set of item type values.

• DISCOUNT
• SALES_TAX
• OTHER_CHARGE

See POST /v3/classifications/items in the API reference for more information.

In the Get list of bills (GET /v3/bills) and Get bills details (GET /v3/bills/{billId}) API response, we have introduced the vendorName field. You can now get the vendor name for each bill with these endpoints.

See GET /v3/bills in the API reference for more information.