#mac-acss-test

1 messages · Page 1 of 1 (latest)

glossy bobcatBOT
naive plover
#

it's all covered in our docs

#

mac-acss-test

frail stirrup
#

ooh i see, so its just specifying the email address in a specific format, k will give that a try thanks!

naive plover
#

sure

frail stirrup
naive plover
#

To help you I need you to be super clear about what you did and how and where. Right now all you said is "doesn't work"

frail stirrup
#

oh sorry by didnt work I mean, it still shows "pending" for the payment:

image.png
naive plover
#

I can't do much with pictures. I can help with real code, developer to developer

frail stirrup
#

i just sent the picture to show you that the payment I made using the bank account was not processed successfully and the email in thebank account billing is: test_skip_waiting_test_email@test.com

naive plover
#

I understand but I can't really infer much from it. So to help you I need you to work with me and provide detailed information about your own code and how you set everything up so that I can then reproduce this and figure out what you need to change, all while helping everyone else!

frail stirrup
#

I see sure, I will send you the API requests I made inorder to create the Bank Account:

**Create SetupIntent and Attach to Customer: **
https://api.stripe.com/v1/setup_intents?payment_method_types[]=acss_debit&customer=cus_XXX&payment_method_options[acss_debit][currency]=cad&payment_method_options[acss_debit][mandate_options][payment_schedule]=interval&payment_method_options[acss_debit][mandate_options][interval_description]=First&payment_method_options[acss_debit][mandate_options][transaction_type]=personal

Confirm SetupIntent:
https://api.stripe.com/v1/setup_intents/seti_XXX/confirm?payment_method_data[type]=acss_debit&payment_method_data[acss_debit][account_number]=000123456789&payment_method_data[acss_debit][institution_number]=000&payment_method_data[acss_debit][transit_number]=11000&payment_method_data[billing_details][name]=Tester&payment_method_data[billing_details][email]=te...@test.com&mandate_data[customer_acceptance][type]=online&mandate_data[customer_acceptance][online][ip_address]=192.168.121.20&mandate_data[customer_acceptance][online][user_agent]=Chrome

After doing this I was able to see the Bank Account for the customer and then tried to make a payment using this bank account and that is when I see the "Pending" status on the payment

#

maybe the email format is still incorrect?

naive plover
#

Sorry I'm struggling so hard to understand what you're even doing

#

are you passing raw bank account details again in the API after we discussed not doing this? :p

#

There are many ways to integrate ACSS so to help you I need you to provide real context (and not just raw HTTP URLs)

frail stirrup
#

yes, but in the docs that is supported and I wanted to create a test bank account, we do not want to use Stripe.JS directly in our app because we are trying to be payment gateway agnostic and that is why we are using a 3rd party library

As you can see in this discussion thread that was recently updated, they are wanting to know if this is a supported flow so that they can add it to there API: https://groups.google.com/g/killbilling-users/c/7nlIxYZd828/m/r82Tbnl7AAAJ

naive plover
#

Yeah but I already told you not to do that and to talk to our support team

frail stirrup
#

As it stands right now we cannot create Canadian Bank Accounts using ACSS

#

using kill bill stripe plugin

naive plover
#

yeah but that's a question for that plugin right? They should be working with us instead? Or you shouldn't use them? Sorry, I'm really struggling to help you, I feel like I'm only getting 10% of what I need to pair with you on this

naive plover
#

@frail stirrup are you still around? Sorry discord was a bit busy but I slowly made progress as I go over time

#

So I did this
1/ Create an ACSS Debit PaymentMethod
2/ Create a SetupIntent + confirm it (with the right PM id and mandate options and such)
3/ Do micro-deposits
=> SetupIntent succeeds instantly

frail stirrup
#

Creating an ACSS Debit PaymentMethod would mean i have to pass raw bank account details too right

#

its the same thing right, the SetupIntent Endpoints that I am using do the same thing, they create the payment method, they attach it to the customer

naive plover
#

I mean you literally shared raw API requests passing raw bank account details

#

I wonder if you are doing SetupIntent then PaymentIntent and just forgot to mention that entirely 😅

frail stirrup
#

nope i only used thse 2 endpoints and that created the bank account on the customer

naive plover
#

but then what is processing?

#

your picture literally had real payments earlier which is completely separate from SetupIntents

frail stirrup
#

oh yes I was testing out the bank account by trying to make a manual payment using that bank account to see if the payments can go through

naive plover
#

😅

#

I just tried and it works fine for me

#

1/ Create an ACSS Debit PaymentMethod
2/ Create a SetupIntent + confirm it (with the right PM id and mandate options and such)
3/ Do micro-deposits
=> SetupIntent succeeds instantly
4/ Create a PaymentIntent and confirm it with that same PaymentMethod id and Mandate id and such
=> processing for a couple seconds and then succeeds