Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Forte to the v3 api #3614

Closed
wsmoak opened this issue May 1, 2020 · 2 comments
Closed

Update Forte to the v3 api #3614

wsmoak opened this issue May 1, 2020 · 2 comments
Labels

Comments

@wsmoak
Copy link
Contributor

wsmoak commented May 1, 2020

The Forte integration is currently using the older v2 api.

Here are the v3 docs: https://restdocs.forte.net/?version=latest

We have this list of tasks:

  1. In the endpoint URI, change v2 to v3
  2. In the endpoint URI, change /accounts to /organizations
  3. In the X-Forte-Auth header change “Account” to “Organization”
  4. Instead of act_XXXXXX use org_XXXXXX
@wsmoak
Copy link
Contributor Author

wsmoak commented May 1, 2020

I gave that a try, but there are still some failures in the remote tests.

Here's the branch: master...wsmoak:forte-api-v3

Note that there are some pre-existing failures on master in the echeck tests, see #3612

wsmoak added a commit to wsmoak/active_merchant that referenced this issue May 26, 2020
Update the Forte gateway to the new v3 API:  https://restdocs.forte.net/?version=latest

* In the endpoint URI, change v2 to v3
* In the endpoint URI, change /accounts to /organizations
* In the X-Forte-Auth header change “Account” to “Organization”
* Allow either organization_id or account_id to be used for configuration for backwards compatibility
* Instead of act_XXXXXX use org_XXXXXX
* remove the unused check_number attribute
* change the 'disburse' action to 'credit'

Fixes: activemerchant#3614

Unit:
20 tests, 67 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed

Remote:
22 tests, 63 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 notifications
100% passed
Copy link

To provide a cleaner slate for the maintenance of the library, this PR/Issue is being labeled stale after 60 days without activity. It will be closed in 14 days unless you comment with an update regarding its applicability to the current build. Thank you!

@github-actions github-actions bot added the Stale label Dec 10, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant